Triple
T10498215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eaton Ford |
E247596
|
entity |
| Predicate | riverBankPosition |
P91384
|
FINISHED |
| Object | western side of the River Great Ouse |
—
|
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: western side of the River Great Ouse | Statement: [Eaton Ford, riverBankPosition, western side of the River Great Ouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankPosition Context triple: [Eaton Ford, riverBankPosition, western side of the River Great Ouse]
-
A.
riverBankOnEastSide
chosen
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
B.
riverBankOnOneSide
Indicates that a river flows adjacent to and borders only one side of a specified bank or land area.
-
C.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
D.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
E.
bridgePosition
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.