Triple
T14057005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOT (Din Offentlige Transport) |
E338244
|
entity |
| Predicate | coordinatesTicketingFor |
P71024
|
FINISHED |
| Object | buses in Greater Copenhagen |
—
|
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: buses in Greater Copenhagen | Statement: [DOT (Din Offentlige Transport), coordinatesTicketingFor, buses in Greater Copenhagen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesTicketingFor Context triple: [DOT (Din Offentlige Transport), coordinatesTicketingFor, buses in Greater Copenhagen]
-
A.
ticketingIssue
Indicates that there is a problem, error, or complication related to a ticketing process or ticket-based system.
-
B.
ticketingCode
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
C.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
D.
ticketOfTarget
Indicates that one entity is a ticket associated with, or issued for, a specific target entity.
-
E.
ticketingResponsibility
chosen
Indicates responsibility for issuing, managing, or handling tickets within a given context or system.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.