Triple
T4215653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokopah Falls |
E94208
|
entity |
| Predicate | hasWaterfallType |
P54800
|
FINISHED |
| Object | cascading waterfall |
—
|
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: cascading waterfall | Statement: [Tokopah Falls, hasWaterfallType, cascading waterfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterfallType Context triple: [Tokopah Falls, hasWaterfallType, cascading waterfall]
-
A.
hasWaterfall
Indicates that one entity possesses, contains, or features a waterfall associated with it.
-
B.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
C.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
D.
waterfallDrop
Indicates a vertical or near-vertical descent of water from a higher level to a lower level, as in a waterfall.
-
E.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
- F. None of above. chosen
Provenance (4 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:04 p.m.