Triple
T17691995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CB postcode area |
E441048
|
entity |
| Predicate | servesTown |
P847
|
FINISHED |
| Object | Linton |
—
|
NE NERFINISHED |
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: Linton | Statement: [CB postcode area, servesTown, Linton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Linton Context triple: [CB postcode area, servesTown, Linton]
-
A.
Linton
Linton is a surname most notably associated with Ralph Linton, an influential American anthropologist known for his work on culture and personality.
-
B.
Linton
chosen
Linton is a village and civil parish in the district of South Cambridgeshire, England, known for its historic high street and rural surroundings.
-
C.
Linton
Linton is a village and civil parish in North Yorkshire, England, falling under the local governance of Craven District Council.
-
D.
Garet
Garet is a given name that functions as a variant form of the name Garrett.
-
E.
Luncarty
Luncarty is a village in Perth and Kinross, Scotland, known historically for its linen bleaching industry and its proximity to the River Tay.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47152306c819086d483d87348db5d |
completed | April 19, 2026, 6:08 a.m. |
Created at: April 10, 2026, 10:03 a.m.