Triple
T30925173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station–Dodger Stadium |
E787835
|
entity |
| Predicate | ticketRequiredForFreeFare |
P138714
|
FINISHED |
| Object | Dodger game ticket |
—
|
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: Dodger game ticket | Statement: [Union Station–Dodger Stadium, ticketRequiredForFreeFare, Dodger game ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketRequiredForFreeFare Context triple: [Union Station–Dodger Stadium, ticketRequiredForFreeFare, Dodger game ticket]
-
A.
accessibleWithoutParkTicket
Indicates that a location, attraction, or service can be reached or used without requiring a park admission ticket.
-
B.
isFreeStandingTicketRequired
chosen
Indicates whether a separate, stand-alone ticket is required for the related item or service.
-
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.
fareRequired
Indicates that a payment or fare is required for access to or use of a service, route, or transportation option.
-
E.
requiresParkTicket
Indicates that access to something is conditional on possessing a valid park ticket.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b82df881909350359a39daa9ff |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.