Triple
T5840702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trikken i Oslo |
E129584
|
entity |
| Predicate | ticketValidityZoneSystem |
P58837
|
FINISHED |
| Object | Ruter 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: Ruter zones | Statement: [Trikken i Oslo, ticketValidityZoneSystem, Ruter zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketValidityZoneSystem Context triple: [Trikken i Oslo, ticketValidityZoneSystem, Ruter zones]
-
A.
validityArea
Indicates the geographic or contextual area within which something (such as a rule, document, or status) is considered valid or in effect.
-
B.
ticketValidityCovers
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
-
C.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
D.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
E.
supportsZoneSystem
chosen
Indicates that one entity provides compatibility with or implementation of a specific zone-based system used by 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.