Triple
T5130787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Harrow |
E115691
|
entity |
| Predicate | hasTransportZone |
P844
|
FINISHED |
| Object | London fare zone 5 |
—
|
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 5 | Statement: [West Harrow, hasTransportZone, London fare zone 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportZone Context triple: [West Harrow, hasTransportZone, London fare zone 5]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasFareZone
chosen
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
C.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
D.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
-
E.
hasZoningPolicy
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.