Triple
T11105108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Sett |
E262607
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Hayfield |
E134064
|
NE 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: Hayfield | Statement: [River Sett, flowsThrough, Hayfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hayfield Context triple: [River Sett, flowsThrough, Hayfield]
-
A.
Hayfield
chosen
Hayfield is a village in Derbyshire, England, known as a gateway to the Peak District and the moorland plateau of Kinder Scout.
-
B.
Homersfield
Homersfield is a small village and civil parish on the River Waveney in eastern England, known for its historic bridge and rural Suffolk setting.
-
C.
Blanefield
Blanefield is a small village in central Scotland, situated near the Campsie Fells and known for its scenic rural setting within the Stirling area.
-
D.
Highfield
Highfield is one of Harare’s oldest and most populous high-density suburbs, historically known as a center of political activism in Zimbabwe.
-
E.
Highfield
Highfield is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2e319881909e66d3c0c73b56bc |
completed | April 9, 2026, 12:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d6d03788190acc9748a3ba0d0ab |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.