Triple
T10186309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London fare zone 4 |
E236917
|
entity |
| Predicate | hasZoneNumber |
P63313
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [London fare zone 4, hasZoneNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoneNumber Context triple: [London fare zone 4, hasZoneNumber, 4]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasFareZoneCode
Indicates that an entity is associated with a specific fare zone identifier used for pricing or tariff purposes.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
railwayZoneNumber
chosen
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded790b488190b1ed4645554873cd |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.