Triple
T20707100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUNCH, Oslo |
E508931
|
entity |
| Predicate | hasExhibitionFloors |
P141170
|
FINISHED |
| Object | 11 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 11 | Statement: [MUNCH, Oslo, hasExhibitionFloors, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionFloors Context triple: [MUNCH, Oslo, hasExhibitionFloors, 11]
-
A.
hasExhibitionArea
Indicates that an entity includes or provides a designated space or area for exhibitions or displays.
-
B.
hasIndoorExhibits
Indicates that an entity provides or contains exhibits that are located indoors.
-
C.
hasExhibits
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
D.
hasExhibitionFunction
Indicates that an entity serves the role or purpose of exhibiting, displaying, or presenting something (e.g., objects, works, or information).
-
E.
hasExhibitionVenue
Indicates that an exhibition is held or hosted at a particular venue.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1917ce08190a54720d4d5b0a02c |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:13 p.m.