Triple
T2394687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan’s Adventure |
E47620
|
entity |
| Predicate | ShiveringTimbersOpeningYear |
P2467
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Michigan’s Adventure, ShiveringTimbersOpeningYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ShiveringTimbersOpeningYear Context triple: [Michigan’s Adventure, ShiveringTimbersOpeningYear, 1998]
-
A.
officialOpeningYear
chosen
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
C.
temporaryWoodenVersionOpened
Indicates that a provisional structure made of wood was opened for use for a limited or interim period.
-
D.
westEndOpeningYear
Indicates the calendar year in which something (typically a production or show) first opened in London’s West End.
-
E.
venueSinceYear
Indicates that a venue has been operating or established since a specified year.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc87827d88190bb2351a688e6de32 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.