Triple
T36545411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nen Hithoel |
E901127
|
entity |
| Predicate | flowsOutTo |
P159234
|
FINISHED |
| Object | Falls of Rauros |
—
|
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: Falls of Rauros | Statement: [Nen Hithoel, flowsOutTo, Falls of Rauros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsOutTo Context triple: [Nen Hithoel, flowsOutTo, Falls of Rauros]
-
A.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
B.
flowsUltimatelyInto
chosen
Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
-
C.
flowsOn
Indicates that one entity (typically a fluid or current) moves continuously along the surface or path defined by another entity.
-
D.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
E.
flowsVia
Indicates that something (such as a substance, signal, or current) moves or is transmitted along, through, or by means of a specified medium, path, or channel.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.