Triple
T31982571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main valley |
E816623
|
entity |
| Predicate | flowsIntoViaMain |
P91112
|
FINISHED |
| Object | Rhine 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: Rhine River | Statement: [Main valley, flowsIntoViaMain, Rhine River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoViaMain Context triple: [Main valley, flowsIntoViaMain, Rhine River]
-
A.
flowsIntoViaMainRiver
chosen
Indicates that one water body ultimately flows into another through the course of a primary or main river channel.
-
B.
flowsUltimatelyInto
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.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsIntoSystem
Indicates that one entity serves as an input or feed that transfers into, and becomes part of, another system.
-
E.
flowsOn
Indicates that one entity (typically a fluid or current) moves continuously along the surface or path defined by another 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34ddbc881909546503b3e11da43 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:12 a.m.