Triple
T26140635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonebridge Park station |
E659504
|
entity |
| Predicate | isInTransportZoneSystem |
P72429
|
FINISHED |
| Object | London Travelcard zones |
—
|
NE NERFINISHED |
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: London Travelcard zones | Statement: [Stonebridge Park station, isInTransportZoneSystem, London Travelcard zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInTransportZoneSystem Context triple: [Stonebridge Park station, isInTransportZoneSystem, London Travelcard zones]
-
A.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
hasFareZoneSystem
chosen
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
D.
isInTransportNetwork
Indicates that an entity is part of, connected to, or contained within a specific transport network or system.
-
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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be435b48190a389ebb5a4537a16 |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:20 p.m.