Triple
T26877077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine River at Angers |
E676780
|
entity |
| Predicate | flowsIntoAtLocation |
P138678
|
FINISHED |
| Object | Loire at Angers |
—
|
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: Loire at Angers | Statement: [Maine River at Angers, flowsIntoAtLocation, Loire at Angers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoAtLocation Context triple: [Maine River at Angers, flowsIntoAtLocation, Loire at Angers]
-
A.
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.
-
B.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
C.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsIntoRegion
chosen
Indicates that a substance, medium, or flow from one entity moves into and enters the spatial area defined by another region.
-
E.
flowsAtBaseOf
Indicates that one entity moves or runs along the lowest part or bottom area of 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f19a7588190b11555c673bbf6a3 |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:36 a.m.