Triple
T27902934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Falls of the Yellowstone River |
E705684
|
entity |
| Predicate | isLargestWaterfallOn |
P42847
|
FINISHED |
| Object | Yellowstone River |
—
|
NE NERFINISHED |
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: Yellowstone River | Statement: [Lower Falls of the Yellowstone River, isLargestWaterfallOn, Yellowstone River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestWaterfallOn Context triple: [Lower Falls of the Yellowstone River, isLargestWaterfallOn, Yellowstone River]
-
A.
majorWaterfall
Indicates that a waterfall is of significant size, height, or volume relative to other waterfalls.
-
B.
isHighestDamIn
Indicates that a dam is the tallest (by height) among all dams located within a specified geographic area or region.
-
C.
waterfallHeight
Indicates the vertical distance or drop in elevation from the top to the bottom of a waterfall.
-
D.
primaryWaterfall
chosen
Indicates that one entity serves as the main or most significant waterfall associated with another entity.
-
E.
hasNumberOfWaterfalls
Indicates the quantity of waterfalls associated with 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:43 p.m.