Triple
T10742542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribuna |
E253362
|
entity |
| Predicate | hasTicketCategory |
P95742
|
FINISHED |
| Object | premium seating area |
—
|
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: premium seating area | Statement: [Tribuna, hasTicketCategory, premium seating area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketCategory Context triple: [Tribuna, hasTicketCategory, premium seating area]
-
A.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
B.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
C.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
D.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
E.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710456ec88190ad8aff8804d13aa9 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.