Triple
T8348936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M20 |
E196109
|
entity |
| Predicate | runsNear |
P350
|
FINISHED |
| Object | Ashford |
E170557
|
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: Ashford | Statement: [M20, runsNear, Ashford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashford Context triple: [M20, runsNear, Ashford]
-
A.
Ashford
Ashford is a large and rapidly growing town in the county of Kent in southeast England, known as a key transport hub with high-speed rail links to London and continental Europe.
-
B.
Ashford
Ashford is a small rural town in northern New South Wales, Australia, known for agriculture and its proximity to natural attractions such as caves and rivers.
-
C.
ASHFORD
chosen
ASHFORD is a town in the borough of Spelthorne in Surrey, England, forming part of the London commuter belt.
-
D.
New Ashford
New Ashford is a small rural town in western Massachusetts, United States, known for its scenic setting in the Berkshires.
-
E.
Bedford
Bedford is a small suburban city located in northeastern Ohio within the Greater Cleveland metropolitan area.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8016c4188190a5ff93078e74dc39 |
completed | March 31, 2026, 8:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc74e11f881908b52d0ffea751c96 |
completed | April 2, 2026, 1:33 a.m. |
Created at: March 30, 2026, 5:58 p.m.