Triple
T14746779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tornado (Wet'n'Wild Gold Coast) |
E346490
|
entity |
| Predicate | rideStructure |
P63555
|
FINISHED |
| Object | elevated tower start |
—
|
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: elevated tower start | Statement: [Tornado (Wet'n'Wild Gold Coast), rideStructure, elevated tower start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideStructure Context triple: [Tornado (Wet'n'Wild Gold Coast), rideStructure, elevated tower start]
-
A.
rideFeature
chosen
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
B.
raceStructure
Indicates a structural or organizational relationship that defines how a race (such as a competition or contest) is arranged, configured, or composed.
-
C.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
rideHeight
Indicates the vertical distance between a vehicle’s chassis and the ground, defining how high it sits relative to the surface.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d116e88190828b163b18d80f68 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.