Triple
T463590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridalveil Fall |
E7394
|
entity |
| Predicate | mistEffect |
P8792
|
FINISHED |
| Object | creates wind-blown spray |
—
|
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: creates wind-blown spray | Statement: [Bridalveil Fall, mistEffect, creates wind-blown spray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mistEffect Context triple: [Bridalveil Fall, mistEffect, creates wind-blown spray]
-
A.
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.
-
B.
involvedPhysicalEffect
chosen
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
C.
primaryEffect
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
D.
tricked
Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
-
E.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc214788190a8dff20fec4412e0 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.