Triple
T17940618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Bishop’s Palace |
E448574
|
entity |
| Predicate | distanceFromWinchesterCathedral |
P59836
|
FINISHED |
| Object | approximately 0.2 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 0.2 miles | Statement: [Old Bishop’s Palace, distanceFromWinchesterCathedral, approximately 0.2 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromWinchesterCathedral Context triple: [Old Bishop’s Palace, distanceFromWinchesterCathedral, approximately 0.2 miles]
-
A.
distanceToWinchester
chosen
Indicates the spatial distance between a given entity and the location identified as Winchester.
-
B.
distanceToWhitchurch
Indicates the spatial distance between a given entity and the location named Whitchurch.
-
C.
distanceToStPaulsCathedral
Indicates the spatial distance between a given entity’s location and St Paul’s Cathedral.
-
D.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
-
E.
distanceToCanterbury
Indicates the spatial distance between a given entity’s location and the location of Canterbury.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad95f4608190b1ebb45944218f07 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.