Triple
T25543254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping to Ongar branch |
E640226
|
entity |
| Predicate | fareZoneCharacteristic |
P99181
|
FINISHED |
| Object | beyond standard London fare zones |
—
|
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: beyond standard London fare zones | Statement: [Epping to Ongar branch, fareZoneCharacteristic, beyond standard London fare zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneCharacteristic Context triple: [Epping to Ongar branch, fareZoneCharacteristic, beyond standard London fare zones]
-
A.
fareZoneDescription
chosen
Indicates the textual description of the fare zone associated with a service, location, or segment.
-
B.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
C.
fareZoneRange
Indicates the range of fare zones within which a ticket, pass, or fare rule is valid or applicable.
-
D.
fareZoneAuthority
Indicates that an authority or organization is responsible for defining, managing, or overseeing a specific fare zone.
-
E.
fareZoneRelation
Indicates a relationship between a location or service and 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895e458819081cf031b70d20e56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:27 p.m.