Triple
T16225838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medusa Steel Coaster |
E393841
|
entity |
| Predicate | reopeningDateAsHybrid |
P82431
|
FINISHED |
| Object | 2014-06-14 |
—
|
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-06-14 | Statement: [Medusa Steel Coaster, reopeningDateAsHybrid, 2014-06-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningDateAsHybrid Context triple: [Medusa Steel Coaster, reopeningDateAsHybrid, 2014-06-14]
-
A.
partialReopeningDate
chosen
Indicates the date on which an entity is reopened in a limited or partial capacity, rather than fully resuming normal operation.
-
B.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
C.
reopeningToPublic
Indicates that an entity, previously closed or restricted, is being opened again for access or use by the general public.
-
D.
reopeningEvent
Indicates an event in which something that was previously closed, suspended, or inactive is opened or made operational again.
-
E.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d25f8bc81909aa59b794a528db2 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.