Triple
T12164071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zone 5 |
E289783
|
entity |
| Predicate | distanceFromCentre |
P103291
|
FINISHED |
| Object | outer ring from Central London |
—
|
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: outer ring from Central London | Statement: [Travelcard Zone 5, distanceFromCentre, outer ring from Central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCentre Context triple: [Travelcard Zone 5, distanceFromCentre, outer ring from Central London]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distanceToCenterField
Indicates the measured distance from a given point or object to the center of a designated field or playing area.
-
C.
distanceFromEarthCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Earth.
-
D.
distanceFromHypocenter
Indicates the measured distance between a specified location and the hypocenter (origin point) of an event such as an earthquake.
-
E.
distanceFromParisCenter
Indicates the measured distance between a given location and the central point of Paris.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.