Triple
T16462889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugs’ White Water Rapids |
E399850
|
entity |
| Predicate | splashEffect |
P16366
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bugs’ White Water Rapids, splashEffect, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: splashEffect Context triple: [Bugs’ White Water Rapids, splashEffect, yes]
-
A.
visualEffect
chosen
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
B.
specialEffectsBy
Indicates that the special effects for something (such as a film, scene, or shot) are created or provided by a particular person or entity.
-
C.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
D.
ashCloudEffect
Indicates the impact or consequences that an ash cloud has on other entities, conditions, or processes.
-
E.
projectionEffect
Indicates the visual or spatial transformation produced when something is projected from one surface, medium, or viewpoint onto another.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d824cd881909b1f2fd40e14ee35 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.