Triple
T710456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Medlock |
E14193
|
entity |
| Predicate | flowsGenerallyDirection |
P19752
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [River Medlock, flowsGenerallyDirection, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsGenerallyDirection Context triple: [River Medlock, flowsGenerallyDirection, west]
-
A.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
flowType
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
-
C.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
E.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a77e42e081909a6f2d1bfdc78ef0 |
completed | March 1, 2026, 8:54 p.m. |
Created at: March 1, 2026, 7:36 p.m.