Triple
T7736680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurlby |
E175399
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Thurlby |
E175399
|
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: Thurlby | Statement: [Thurlby, civilParish, Thurlby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thurlby Context triple: [Thurlby, civilParish, Thurlby]
-
A.
Thurlby
chosen
Thurlby is a village and civil parish in the South Kesteven district of Lincolnshire, England.
-
B.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
C.
Peddle Thorp
Peddle Thorp is an Australian architectural firm known for designing a wide range of commercial, residential, and public buildings.
-
D.
Barnetby
Barnetby is a village and railway junction in North Lincolnshire, England, known for its busy rail connections on routes across northern and eastern England.
-
E.
Tilbrook
Tilbrook is a small rural village and civil parish in Cambridgeshire, England, situated near the historic town of Kimbolton.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7035923108190842025631e2314cc |
completed | March 27, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be3958ac8190a48ba07bd8ea3251 |
completed | March 29, 2026, 5:52 a.m. |
Created at: March 27, 2026, 4:07 p.m.