Triple
T5902303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kesteven |
E131255
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Navenby |
E402831
|
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: Navenby | Statement: [Kesteven, containsSettlement, Navenby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Navenby Context triple: [Kesteven, containsSettlement, Navenby]
-
A.
Navenby
chosen
Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
-
B.
Barrowby
Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
-
C.
Barnby
Barnby is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
D.
Narborough
Narborough is a village in Leicestershire, England, known as a suburban commuter settlement near Leicester with historical roots and local amenities.
-
E.
Narborough
Narborough is a village in the English county of Norfolk, known for its rural setting and historic parish 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03735e6f8819084eded3b45f5e4ed |
completed | March 22, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0c0076cd88190b10e51c52dcc6a2e |
completed | March 23, 2026, 4:22 a.m. |
Created at: March 22, 2026, 3:58 p.m.