Triple
T6479350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lark |
E146148
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Tuddenham |
E299727
|
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: Tuddenham | Statement: [River Lark, nearbySettlement, Tuddenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tuddenham Context triple: [River Lark, nearbySettlement, Tuddenham]
-
A.
Tuddenham
chosen
Tuddenham is a village and civil parish located in the county of Suffolk in eastern England.
-
B.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
C.
Manton
Manton is a neighborhood and village area located within Providence County in the state of Rhode Island.
-
D.
Blatchford
Blatchford is a sustainable, mixed-use residential community being developed on the former Edmonton City Centre Airport lands in Edmonton, Alberta.
-
E.
Hannington
Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4e764c819086828bb841f588e0 |
completed | March 22, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c653aceb8c8190aff0abf15b049737 |
completed | March 27, 2026, 9:53 a.m. |
Created at: March 22, 2026, 4:51 p.m.