Triple
T6079140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo public transport network |
E135477
|
entity |
| Predicate | usesFareZones |
P54839
|
FINISHED |
| Object | zone-based fare system |
—
|
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: zone-based fare system | Statement: [Oslo public transport network, usesFareZones, zone-based fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFareZones Context triple: [Oslo public transport network, usesFareZones, zone-based fare system]
-
A.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
B.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
-
C.
hasFareZoneCode
Indicates that an entity is associated with a specific fare zone identifier used for pricing or tariff purposes.
-
D.
fareZoneUsage
chosen
Indicates how a fare zone is applied or utilized within a transportation or pricing context.
-
E.
hasFormerFareZone
Indicates that an entity was previously assigned to a particular fare zone, but is no longer in that fare zone.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.