Triple
T2357758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Cascades |
E47196
|
entity |
| Predicate | hasPositionInWaterfall |
P8266
|
FINISHED |
| Object | middle section of Yosemite Falls |
—
|
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: middle section of Yosemite Falls | Statement: [Middle Cascades, hasPositionInWaterfall, middle section of Yosemite Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInWaterfall Context triple: [Middle Cascades, hasPositionInWaterfall, middle section of Yosemite Falls]
-
A.
hasWaterfall
Indicates that one entity possesses, contains, or features a waterfall associated with it.
-
B.
hasBottomWater
Indicates that an entity contains or is associated with water specifically located at its bottom or lowest part.
-
C.
hasPositionOn
chosen
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
D.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
E.
waterfallDrop
Indicates a vertical or near-vertical descent of water from a higher level to a lower level, as in a waterfall.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc71f767481908dfa9be209ea3c5a |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.