Triple
T13916387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary’s Church, Market Drayton |
E334631
|
entity |
| Predicate | locatedIn |
P40
|
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: [St Mary’s Church, Market Drayton, locatedIn, Market Drayton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Market Drayton Context triple: [St Mary’s Church, Market Drayton, locatedIn, 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.
Drayton
Drayton is a village in Norfolk, England, situated near the city of Norwich along the River Wensum.
-
D.
Drayton
Drayton is a residential suburb in the northern part of Portsmouth, England.
-
E.
Drayton Park
Drayton Park is a residential area and railway station in Highbury, North London, located close to Arsenal’s Emirates Stadium.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac85fd7c819089e7a78dcf0b22fb |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:16 p.m.