Triple
T30042425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoke Mandeville |
E763349
|
entity |
| Predicate | distanceFromAylesbury |
P105224
|
FINISHED |
| Object | approximately 3 miles |
—
|
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 3 miles | Statement: [Stoke Mandeville, distanceFromAylesbury, approximately 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAylesbury Context triple: [Stoke Mandeville, distanceFromAylesbury, approximately 3 miles]
-
A.
distanceToAylesbury
chosen
Indicates the spatial distance between a given entity and the location of Aylesbury.
-
B.
distanceFromWellingborough
Indicates the spatial distance measured from the reference location Wellingborough to another place or entity.
-
C.
distanceFromAvebury
Indicates the measured distance between a given entity and the location of Avebury.
-
D.
distanceToHemelHempstead
Indicates the spatial distance between a given entity and the location of Hemel Hempstead.
-
E.
distanceFromWokingham
Indicates the measured distance between a given entity or location and Wokingham.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: April 29, 2026, 6:53 p.m.