Triple
T3385591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Paul’s Underground station |
E71292
|
entity |
| Predicate | distanceToStPaulsCathedral |
P47153
|
FINISHED |
| Object | approximately 120 metres |
—
|
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 120 metres | Statement: [St Paul’s Underground station, distanceToStPaulsCathedral, approximately 120 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStPaulsCathedral Context triple: [St Paul’s Underground station, distanceToStPaulsCathedral, approximately 120 metres]
-
A.
distanceToWashingtonMonument
Indicates the physical distance between a given entity’s location and the Washington Monument.
-
B.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
C.
distanceToRunnymede
Indicates the spatial distance between a given entity or location and Runnymede.
-
D.
distanceToCanterbury
Indicates the spatial distance between a given entity’s location and the location of Canterbury.
-
E.
distanceToStAlbans
Indicates the measured distance between a given entity’s location and the location of St Albans.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ee5e188190912dcea494a12038 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.