Triple
T7842007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A576 road |
E181827
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Middleton |
E30354
|
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: Middleton | Statement: [A576 road, serves, Middleton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Middleton Context triple: [A576 road, serves, Middleton]
-
A.
Middleton
Middleton is a small coastal town in South Australia known for its surf beaches and holiday atmosphere.
-
B.
Middleton
chosen
Middleton is a town in Greater Manchester, England, historically part of Lancashire and now a residential and industrial suburb of Manchester.
-
C.
Middleton
Middleton is a village and civil parish in the English county of Norfolk, situated near the town of King’s Lynn.
-
D.
Middleton
Middleton is a British family name historically associated with the lineage of Lord Barham and other notable figures in the United Kingdom.
-
E.
Middleton
Middleton is a suburban city in south-central Wisconsin, known for its proximity to Madison and its mix of residential neighborhoods, parks, and commercial areas.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c6cbe48190b73df491de1004c3 |
completed | March 31, 2026, 12:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5ad44ff081908954395aef6ac78b |
completed | March 31, 2026, 5:25 a.m. |
Created at: March 30, 2026, 4:48 p.m.