Triple
T2293577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petts Wood |
E51559
|
entity |
| Predicate | timeToCentralLondonByTrain |
P39021
|
FINISHED |
| Object | approximately 25–35 minutes |
—
|
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 25–35 minutes | Statement: [Petts Wood, timeToCentralLondonByTrain, approximately 25–35 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToCentralLondonByTrain Context triple: [Petts Wood, timeToCentralLondonByTrain, approximately 25–35 minutes]
-
A.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
B.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or period.
-
C.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
E.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:48 p.m.