Triple
T18596417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARoS Aarhus Art Museum |
E454504
|
entity |
| Predicate | reopenedInCurrentBuilding |
P40520
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [ARoS Aarhus Art Museum, reopenedInCurrentBuilding, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedInCurrentBuilding Context triple: [ARoS Aarhus Art Museum, reopenedInCurrentBuilding, 2004]
-
A.
reopenedInNewBuilding
Indicates that an entity, after being closed or relocated, has resumed operations in a different, newly constructed building.
-
B.
openedAsCurrentBuilding
Indicates that an entity began operating or was inaugurated in its current building or physical premises.
-
C.
reopenedInCurrentLocation
chosen
Indicates that an entity, after having been closed or moved, has been opened again at its present location.
-
D.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
E.
reopensIn
Indicates that an entity resumes operation or becomes accessible again at a specified time or under specified conditions after having been closed or inactive.
- F. None of above.
Provenance (3 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474ce0c08190b440cbe86b6ef7b9 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.