Triple
T21731628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riptide Racer |
E536419
|
entity |
| Predicate | hasRideFormat |
P120070
|
FINISHED |
| Object | competitive |
—
|
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: competitive | Statement: [Riptide Racer, hasRideFormat, competitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideFormat Context triple: [Riptide Racer, hasRideFormat, competitive]
-
A.
hasRideEnvironment
Indicates that an entity is associated with, or takes place within, a particular ride-related environment or setting.
-
B.
containsRideType
Indicates that one entity includes or offers a specific type or category of ride as part of its available options.
-
C.
hasRaceFormat
chosen
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
D.
hasTicketFormat
Indicates that an entity’s ticket is expressed or structured in a particular format.
-
E.
hasSubRide
Indicates that a ride or journey is composed of, or includes, one or more smaller component rides or segments.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0713c48190a38b3963cb3cbaf0 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.