Triple
T21003536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egypt (Busch Gardens Tampa Bay) |
E517353
|
entity |
| Predicate | hasPrimaryCoasterType |
P63789
|
FINISHED |
| Object | inverted roller coaster |
—
|
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: inverted roller coaster | Statement: [Egypt (Busch Gardens Tampa Bay), hasPrimaryCoasterType, inverted roller coaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCoasterType Context triple: [Egypt (Busch Gardens Tampa Bay), hasPrimaryCoasterType, inverted roller coaster]
-
A.
coasterType
Indicates the specific category or style of a coaster that characterizes its design or function.
-
B.
hasPrimaryAttractionType
Indicates that an entity is characterized by a main or dominant type of attraction or appeal it offers.
-
C.
rollerCoasterType
chosen
Indicates that one entity is classified as a specific type or category of roller coaster in relation to another entity.
-
D.
COASTERIs
Indicates that one entity is a coaster or functions in the role of a coaster in relation to 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3978b0819082b63a98962a673e |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.