Triple
T20086592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teddington Lock |
E496147
|
entity |
| Predicate | distanceFromTeddingtonRailwayStation |
P138669
|
FINISHED |
| Object | about 1 mile |
—
|
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: about 1 mile | Statement: [Teddington Lock, distanceFromTeddingtonRailwayStation, about 1 mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTeddingtonRailwayStation Context triple: [Teddington Lock, distanceFromTeddingtonRailwayStation, about 1 mile]
-
A.
riverMileFromTeddington
Indicates the distance in river miles of a location measured upstream from Teddington.
-
B.
distanceToEgham
Indicates the spatial distance between a given entity and the location of Egham.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
distanceToHemelHempstead
Indicates the spatial distance between a given entity and the location of Hemel Hempstead.
-
E.
distanceFromBakerStreet
Indicates the measured spatial distance between a given entity and Baker Street.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ba40c8190adea0e271a1249cf |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:04 p.m.