Triple
T27168593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studley |
E682843
|
entity |
| Predicate | distanceToStratford-upon-Avon |
P170598
|
FINISHED |
| Object | approximately 13 miles north-west |
—
|
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: approximately 13 miles north-west | Statement: [Studley, distanceToStratford-upon-Avon, approximately 13 miles north-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStratford-upon-Avon Context triple: [Studley, distanceToStratford-upon-Avon, approximately 13 miles north-west]
-
A.
distanceToStratfordUponAvon
chosen
Indicates the spatial distance between a given entity’s location and Stratford-upon-Avon.
-
B.
distanceToStroud
Indicates the spatial distance between a given entity or location and the place named Stroud.
-
C.
distanceToCoventry
Indicates the measured or specified distance between a given entity’s location and the city of Coventry.
-
D.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
E.
distanceToWarwick
Indicates the spatial distance between a given entity and the location Warwick.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 27, 2026, 9:22 a.m.