Triple
T1453477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen Line |
E31344
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Watlington |
E49608
|
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: Watlington | Statement: [Fen Line, passesThrough, Watlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Watlington Context triple: [Fen Line, passesThrough, Watlington]
-
A.
Watlington
chosen
Watlington is a village in Norfolk, England, known for its rural character and location near the River Great Ouse.
-
B.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
C.
Langworthy
Langworthy is a residential district in Salford, Greater Manchester, known for its urban regeneration and proximity to Manchester city centre.
-
D.
Owerton
Owerton is an alternative spelling of the name Overton, which is used for various places and surnames in English-speaking regions.
-
E.
Rushworth
Rushworth is the middle name of Lord Jellicoe, a British naval officer and statesman who served as First Sea Lord during World War I.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57e82d48190a30a4512f39f5de0 |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e71ffd481909dfd0f77201dc17c |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 8 p.m.