Triple
T11086969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderhawk (Michigan's Adventure) |
E262144
|
entity |
| Predicate | relocation |
P1659
|
FINISHED |
| Object | relocated from Geauga Lake to Michigan's Adventure |
—
|
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: relocated from Geauga Lake to Michigan's Adventure | Statement: [Thunderhawk (Michigan's Adventure), relocation, relocated from Geauga Lake to Michigan's Adventure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocation Context triple: [Thunderhawk (Michigan's Adventure), relocation, relocated from Geauga Lake to Michigan's Adventure]
-
A.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
B.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
C.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
-
D.
relocatedFrom
chosen
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c3ed9c8190a3f5cdf1fe0e74a2 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.