Triple
T3162422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Drayton |
E66130
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | MARKET DRAYTON |
E66130
|
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: MARKET DRAYTON | Statement: [Market Drayton, hasPostTown, MARKET DRAYTON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MARKET DRAYTON Context triple: [Market Drayton, hasPostTown, MARKET DRAYTON]
-
A.
Market Drayton
chosen
Market Drayton is a historic market town in Shropshire, England, known for its traditional markets and rural surroundings.
-
B.
Drayton
Drayton is a village in Oxfordshire, England, situated within the Vale of White Horse district.
-
C.
Mulbarton
Mulbarton is a village and civil parish in South Norfolk, England, situated a few miles south of the city of Norwich.
-
D.
Market Harborough
Market Harborough is a market town in Leicestershire, England, known for its historic center and role as a regional commercial and transport hub.
-
E.
Mottingham
Mottingham is a suburban district in southeast London, England, known for its residential character and green spaces.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada618b9b88190afaa6d47dcad9f2c |
completed | March 8, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235d07ad88190838a845b5ade05a0 |
completed | March 12, 2026, 3:41 a.m. |
Created at: March 8, 2026, 3:06 p.m.