Triple
T32072861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VRR |
E819061
|
entity |
| Predicate | coordinatesTicketing |
P178846
|
FINISHED |
| Object | integrated ticketing 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: integrated ticketing system | Statement: [VRR, coordinatesTicketing, integrated ticketing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesTicketing Context triple: [VRR, coordinatesTicketing, integrated ticketing system]
-
A.
ticketingForm
Indicates a relationship where a ticket is associated with a specific form used to capture or manage its details.
-
B.
ticketedBy
Indicates that an entity has been issued or assigned a ticket by another entity (such as an authority, system, or agent).
-
C.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
D.
ticketingIssue
Indicates that there is a problem, error, or complication related to a ticketing process or ticket-based system.
-
E.
ticketingFor
Indicates that one entity is responsible for issuing, managing, or providing tickets for another entity, such as an event, service, or venue.
- F. None of above. chosen
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: May 1, 2026, 12:23 a.m.