Triple
T10568468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girton |
E249413
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Histon |
E203259
|
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: Histon | Statement: [Girton, hasNearbySettlement, Histon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Histon Context triple: [Girton, hasNearbySettlement, Histon]
-
A.
Histon
chosen
Histon is a large village and civil parish in Cambridgeshire, England, situated just north of Cambridge and known for its residential community and local amenities.
-
B.
Hamstead
Hamstead is a suburban residential area in the West Midlands, England, situated between Birmingham and Sandwell.
-
C.
Amersham
Amersham is a historic market town in southeast England known for its picturesque old town, Chilterns countryside setting, and role as a commuter hub into London.
-
D.
Hanham
Hanham is a suburban village and residential area on the eastern edge of Bristol in South West England.
-
E.
Harpenden
Harpenden is a commuter town in southern England known for its green spaces and affluent residential 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ff53c8190ae7c399d49b585f5 |
completed | April 7, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b4c26ec8190910efdf4a236d654 |
completed | April 10, 2026, 7:11 p.m. |
Created at: April 6, 2026, 12:37 p.m.