Triple
T7969293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom Buggy |
E185283
|
entity |
| Predicate | rideSystemType |
P23569
|
FINISHED |
| Object | Omnimover |
—
|
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: Omnimover | Statement: [Doom Buggy, rideSystemType, Omnimover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideSystemType Context triple: [Doom Buggy, rideSystemType, Omnimover]
-
A.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
bicycleType
Indicates the specific kind or category of bicycle associated with an entity.
-
D.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
-
E.
hasRideSystem
chosen
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.