Triple
T15315263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD postcode area |
E366138
|
entity |
| Predicate | containsPostTown |
P2711
|
FINISHED |
| Object | Earlston |
E324597
|
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: Earlston | Statement: [TD postcode area, containsPostTown, Earlston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Earlston Context triple: [TD postcode area, containsPostTown, Earlston]
-
A.
Earlston
chosen
Earlston is a small rural village in the Scottish Borders region of southeastern Scotland.
-
B.
Earlstoun
Earlstoun is the Scots-language name for the town of Earlston in the Scottish Borders.
-
C.
Eddleston
Eddleston is a small rural village in the Scottish Borders region of Scotland, known for its scenic surroundings and historic parish church.
-
D.
Earlton
Earlton is a small rural community in northeastern Ontario, Canada, known for its agricultural surroundings and proximity to the city of Temiskaming Shores.
-
E.
Humberston
Humberston is a coastal village and civil parish in North East Lincolnshire, England, known for its proximity to the North Sea and the nearby resort of Cleethorpes.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd050108190a584543cb93943a4 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8a688a48190848eb7f065aba146 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.