Triple
T20507267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota Heritage Center & State Museum |
E503466
|
entity |
| Predicate | reopenedAfterExpansion |
P34772
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [North Dakota Heritage Center & State Museum, reopenedAfterExpansion, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterExpansion Context triple: [North Dakota Heritage Center & State Museum, reopenedAfterExpansion, 2014]
-
A.
reopenedAfter
chosen
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
B.
fullyReopened
Indicates that something previously closed or partially open has been restored to complete, unrestricted operational status.
-
C.
wasExpanded
Indicates that something increased in size, scope, or extent compared to its previous state.
-
D.
reopenedFor
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
E.
wasExpandedIn
Indicates that something increased in size, scope, or extent during a specified time or event.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc82dd0819085d64d65a1e72c70 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:36 a.m.