Triple
T3299719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreamworld |
E69298
|
entity |
| Predicate | hasIncident |
P18677
|
FINISHED |
| Object | Thunder River Rapids Ride accident |
—
|
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: Thunder River Rapids Ride accident | Statement: [Dreamworld, hasIncident, Thunder River Rapids Ride accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncident Context triple: [Dreamworld, hasIncident, Thunder River Rapids Ride accident]
-
A.
hasNotableIncident
chosen
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
B.
hasIncidence
Indicates that a particular event, condition, or phenomenon occurs at a certain rate, frequency, or number of cases within a defined population or context.
-
C.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
E.
hasSecurityEvent
Indicates that a security-related incident or event is associated with, or has occurred for, a given entity.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.