Triple
T37484466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Wallace Falls |
E931492
|
entity |
| Predicate | positionInWaterfallSystem |
P37757
|
FINISHED |
| Object | lowest tier |
—
|
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: lowest tier | Statement: [Lower Wallace Falls, positionInWaterfallSystem, lowest tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInWaterfallSystem Context triple: [Lower Wallace Falls, positionInWaterfallSystem, lowest tier]
-
A.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
B.
positionInCascade
chosen
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
C.
positionOnSystem
Indicates the relative location or placement of an entity within a larger structured system or framework.
-
D.
positionInCanal
Indicates that an entity occupies a specific location within a canal.
-
E.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:17 p.m.