Triple
T35204470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford, Northamptonshire |
E1016495
|
entity |
| Predicate | distanceToDaventry |
P206874
|
FINISHED |
| Object | approximately 7 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 7 miles | Statement: [Watford, Northamptonshire, distanceToDaventry, approximately 7 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDaventry Context triple: [Watford, Northamptonshire, distanceToDaventry, approximately 7 miles]
-
A.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
-
B.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
C.
distanceToHitchin
Indicates the measured spatial distance between a given entity and the location identified as Hitchin.
-
D.
distanceToOswestry
Indicates the spatial distance between a given entity and the location of Oswestry.
-
E.
distanceToOundle
Indicates the spatial distance between a given entity and the location of Oundle.
- F. None of above. chosen
Provenance (4 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.