Triple
T6849280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Association |
E157973
|
entity |
| Predicate | ticketPricePolicy |
P72590
|
FINISHED |
| Object | lower than National League |
—
|
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: lower than National League | Statement: [American Association, ticketPricePolicy, lower than National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPricePolicy Context triple: [American Association, ticketPricePolicy, lower than National League]
-
A.
ticketPricePlanned
Indicates that a ticket has an intended or scheduled price set in advance, as opposed to its actual or current selling price.
-
B.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
C.
ticketClassSystem
Indicates that an entity is classified within a particular ticketing or fare class system that defines categories or levels of tickets.
-
D.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
E.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84acb288190a67d974197ecab2f |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:20 p.m.