Triple
T19976021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashopton |
E493691
|
entity |
| Predicate | transportRouteNearbyHistoric |
P115769
|
FINISHED |
| Object | road between Sheffield and Glossop |
—
|
LITERAL 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: road between Sheffield and Glossop | Statement: [Ashopton, transportRouteNearbyHistoric, road between Sheffield and Glossop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRouteNearbyHistoric Context triple: [Ashopton, transportRouteNearbyHistoric, road between Sheffield and Glossop]
-
A.
nearHistoricalRoute
chosen
Indicates that one entity is located close to a historically significant route or pathway.
-
B.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
C.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
D.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
E.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
- F. None of above.
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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d0f4fb48190ad63afeff3513523 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:26 p.m.