Triple
T34163822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finchley Road & Frognal railway station |
E876353
|
entity |
| Predicate | distanceToValue |
P205345
|
FINISHED |
| Object | approximately 300 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 300 metres | Statement: [Finchley Road & Frognal railway station, distanceToValue, approximately 300 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToValue Context triple: [Finchley Road & Frognal railway station, distanceToValue, approximately 300 metres]
-
A.
distanceFromPoti
Indicates the measured spatial distance between a given entity and the location of Poti.
-
B.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
-
C.
distanceFromStart
Indicates the measured distance between an entity’s current position and its starting point.
-
D.
distanceToTerminal
Indicates the measured or calculated distance from a given entity or location to a specified terminal point or facility.
-
E.
distanceToTenby
Indicates the spatial distance between a given entity or location and the town of Tenby.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:54 a.m.