Triple
T14746758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tornado (Wet'n'Wild Gold Coast) |
E346490
|
entity |
| Predicate | dropElement |
P115614
|
FINISHED |
| Object | steep enclosed drop |
—
|
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: steep enclosed drop | Statement: [Tornado (Wet'n'Wild Gold Coast), dropElement, steep enclosed drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dropElement Context triple: [Tornado (Wet'n'Wild Gold Coast), dropElement, steep enclosed drop]
-
A.
dropStyle
Indicates the manner or pattern in which something is dropped, such as how an item or element is released or falls.
-
B.
dropSource
Indicates that an entity serves as the origin or starting point from which something is dropped, released, or caused to fall.
-
C.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
-
D.
drop
Indicates that an entity causes something to fall or be released from a higher position to a lower one.
-
E.
dropCondition
Indicates that an entity ceases to satisfy, or is no longer subject to, a specified condition or requirement.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.