Triple
T26590422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergkrystallen station |
E667336
|
entity |
| Predicate | hasTicketZoneAuthority |
P80768
|
FINISHED |
| Object | Ruter |
—
|
NE NERFINISHED |
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 | Statement: [Bergkrystallen station, hasTicketZoneAuthority, Ruter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketZoneAuthority Context triple: [Bergkrystallen station, hasTicketZoneAuthority, Ruter]
-
A.
hasTicketZoneOperator
Indicates that a ticket zone is managed, controlled, or operated by a specific operator.
-
B.
hasTicketingAuthority
chosen
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
-
C.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
D.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
-
E.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 2:07 a.m.