Triple
T4563686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephant and Castle |
E121856
|
entity |
| Predicate | inLondonTravelcardZone |
P17300
|
FINISHED |
| Object | Zone 1 |
—
|
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: Zone 1 | Statement: [Elephant and Castle, inLondonTravelcardZone, Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inLondonTravelcardZone Context triple: [Elephant and Castle, inLondonTravelcardZone, Zone 1]
-
A.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
B.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
-
C.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
-
D.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
E.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd5830b4308190a63699bf28922375 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.