Triple
T13656568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Cod Baseball League |
E326874
|
entity |
| Predicate | ticketPriceGeneral |
P3997
|
FINISHED |
| Object | donation-based or low-cost admission |
—
|
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: donation-based or low-cost admission | Statement: [Cape Cod Baseball League, ticketPriceGeneral, donation-based or low-cost admission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPriceGeneral Context triple: [Cape Cod Baseball League, ticketPriceGeneral, donation-based or low-cost admission]
-
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.
ticketPricePolicy
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.
admissionFee
chosen
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
E.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61d56e4819084ae3c16ecdf4a05 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.