Triple
T19176323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL preseason games |
E469445
|
entity |
| Predicate | hasTicketPricing |
P72590
|
FINISHED |
| Object | often similar to regular season pricing |
—
|
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: often similar to regular season pricing | Statement: [NFL preseason games, hasTicketPricing, often similar to regular season pricing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketPricing Context triple: [NFL preseason games, hasTicketPricing, often similar to regular season pricing]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
ticketPricePolicy
chosen
Indicates the pricing rules or conditions that determine how much a ticket costs in a given context.
-
C.
ticketPricingLevel
Indicates the pricing tier or category assigned to a ticket within a defined pricing structure.
-
D.
hasTicketOption
Indicates that an entity offers or is associated with a particular ticket choice or type as an available option.
-
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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f6181f0c8190b344072db0b7abbb |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.