Triple
T30664058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotel Breakers |
E780608
|
entity |
| Predicate | locatedInAmusementPark |
P202950
|
FINISHED |
| Object | Cedar Point |
—
|
NE NERFINISHED |
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: Cedar Point | Statement: [Hotel Breakers, locatedInAmusementPark, Cedar Point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAmusementPark Context triple: [Hotel Breakers, locatedInAmusementPark, Cedar Point]
-
A.
locatedInThemeParkType
Indicates that an entity is situated within or belongs to a specific type or category of theme park.
-
B.
locatedInAttractionScene
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
-
C.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
D.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
E.
themeParkAttractionLocation
Indicates the specific place or area within a theme park where a particular attraction is situated.
- F. None of above. chosen
Provenance (4 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00d508290081909f3d5dfbb2e80c8e |
completed | May 10, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_6a00d49da4cc81909566ad286ec22292 |
completed | May 10, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_6a00d5073e188190b09916119a9c032d |
completed | May 10, 2026, 6:57 p.m. |
Created at: April 29, 2026, 8:31 p.m.