Triple
T7598559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big One |
E179921
|
entity |
| Predicate | coasterStyle |
P63190
|
FINISHED |
| Object | traditional chain-lift hypercoaster |
—
|
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: traditional chain-lift hypercoaster | Statement: [The Big One, coasterStyle, traditional chain-lift hypercoaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coasterStyle Context triple: [The Big One, coasterStyle, traditional chain-lift hypercoaster]
-
A.
coasterType
chosen
Indicates the specific category or style of a coaster that characterizes its design or function.
-
B.
rollerCoasterType
Indicates that one entity is classified as a specific type or category of roller coaster in relation to another entity.
-
C.
isFamilyCoaster
Indicates that a roller coaster is designed to be suitable and enjoyable for riders of all ages, including children and families.
-
D.
hasSimilarCoaster
Indicates that one entity possesses or is associated with a coaster that is similar in characteristics or design to a coaster possessed or associated with another entity.
-
E.
hasRollerCoaster
Indicates that one entity possesses, contains, or features a roller coaster as part of it.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d67cf88190a3202c07f7cea7df |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.