Triple
T7084156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cunsey Beck |
E165032
|
entity |
| Predicate | flowsIntoPart |
P73474
|
FINISHED |
| Object | southern part of Windermere |
—
|
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: southern part of Windermere | Statement: [Cunsey Beck, flowsIntoPart, southern part of Windermere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoPart Context triple: [Cunsey Beck, flowsIntoPart, southern part of Windermere]
-
A.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
B.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
C.
flowsIntoSystem
chosen
Indicates that one entity serves as an input or feed that transfers into, and becomes part of, another system.
-
D.
flowsOver
Indicates that one substance or medium moves across the surface or boundary of another, covering or passing above it.
-
E.
flowsParallelTo
Indicates that one entity moves or extends in the same direction as another without intersecting it, maintaining a parallel course.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5102be08190bbde790bfa8fe9e2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.