Triple
T20713133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Throttle |
E509096
|
entity |
| Predicate | RCDBNumber |
P78084
|
FINISHED |
| Object | 1080 |
—
|
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: 1080 | Statement: [Full Throttle, RCDBNumber, 1080]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RCDBNumber Context triple: [Full Throttle, RCDBNumber, 1080]
-
A.
hasRcdbNumber
chosen
Indicates that an entity is associated with a specific RCDB (Roller Coaster DataBase) identification number.
-
B.
BDNumber
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
-
C.
ringNumber
Indicates that an entity is assigned a specific ring identifier or position number within a ring-structured system or sequence.
-
D.
databaseIntroducedIn
Indicates the point in time, version, or context in which a particular database was first introduced or made available.
-
E.
recordIdentification
Indicates that an entity assigns or maintains a unique identifier or set of identifying information for a specific record.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ce84e48190922db93ed4b5d21b |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.