Triple
T10088073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorleywood |
E215269
|
entity |
| Predicate | railZone |
P24188
|
FINISHED |
| Object | London fare zone 7 |
—
|
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 7 | Statement: [Chorleywood, railZone, London fare zone 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railZone Context triple: [Chorleywood, railZone, London fare zone 7]
-
A.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
B.
hasRailwayZone
chosen
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
C.
railwayZoneHeadquartersFor
Indicates that a location serves as the administrative headquarters for a particular railway zone.
-
D.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
E.
railwayDivision
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.