Triple
T26081003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tottenham Hale bus station |
E657840
|
entity |
| Predicate | inTransportZone |
P106124
|
FINISHED |
| Object | London fare zone 3 |
—
|
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: London fare zone 3 | Statement: [Tottenham Hale bus station, inTransportZone, London fare zone 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTransportZone Context triple: [Tottenham Hale bus station, inTransportZone, London fare zone 3]
-
A.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
-
B.
locatedInTransportArea
chosen
Indicates that an entity is situated within a designated transport-related area or zone.
-
C.
transportedBetween
Indicates that an entity is moved or conveyed from one specified location or state to another.
-
D.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
-
E.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606fbaacc81909bc7b9ead4967b41 |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:38 p.m.