Triple
T23396979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claremont Museum of Art |
E559385
|
entity |
| Predicate | reopenedAtCurrentLocation |
P40520
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Claremont Museum of Art, reopenedAtCurrentLocation, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAtCurrentLocation Context triple: [Claremont Museum of Art, reopenedAtCurrentLocation, 2016]
-
A.
reopenedInCurrentLocation
chosen
Indicates that an entity, after having been closed or moved, has been opened again at its present location.
-
B.
openedAtCurrentLocation
Indicates that an entity has been opened or initiated at the user’s or system’s current physical or contextual location.
-
C.
reopenedForNavigation
Indicates that something previously closed to traffic or passage has been opened again for navigational use.
-
D.
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.
-
E.
reopenedOnSiteOf
Indicates that something has been reopened at the same physical location where it previously existed or operated.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dc48008190bdcf92f8d9a5232d |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.