Triple
T7009497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tissington Trail |
E162543
|
entity |
| Predicate | hasTrailhead |
P3625
|
FINISHED |
| Object | Ashbourne |
E141493
|
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: Ashbourne | Statement: [Tissington Trail, hasTrailhead, Ashbourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashbourne Context triple: [Tissington Trail, hasTrailhead, Ashbourne]
-
A.
Ashbourne
chosen
Ashbourne is a historic market town in Derbyshire, England, known for its traditional architecture and annual Royal Shrovetide Football match.
-
B.
Ashby
Ashby is a small rural community located within the township of Addington Highlands in eastern Ontario, Canada.
-
C.
Ashby
Ashby is a surname most notably associated with Hal Ashby, the influential American film director known for 1970s classics such as "Harold and Maude" and "Being There."
-
D.
Ashby
Ashby is a small town in north-central Massachusetts, United States, known for its rural character and proximity to the city of Fitchburg.
-
E.
Ashover
Ashover is a rural village and civil parish in Derbyshire, England, known for its scenic countryside and historic stone buildings.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc38039c8190ab420d62bb11b4d9 |
completed | March 27, 2026, 7:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c775612fe88190822f297f2bec6cd1 |
completed | March 28, 2026, 6:29 a.m. |
Created at: March 27, 2026, 2:34 p.m.