Triple
T6372613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemble |
E143386
|
entity |
| Predicate | distanceToLondonPaddingtonByRail |
P39021
|
FINISHED |
| Object | about 75 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: about 75 minutes | Statement: [Kemble, distanceToLondonPaddingtonByRail, about 75 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLondonPaddingtonByRail Context triple: [Kemble, distanceToLondonPaddingtonByRail, about 75 minutes]
-
A.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
B.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
C.
timeToCentralLondonByTrain
chosen
Indicates the amount of time it takes to travel by train from a given location to central London.
-
D.
distanceToEgham
Indicates the spatial distance between a given entity and the location of Egham.
-
E.
distanceToByRail
Indicates the distance between two locations when traveling via railway routes.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.