Triple
T37474246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic City Classic |
E931236
|
entity |
| Predicate | hasHalftimeEvent |
P10817
|
FINISHED |
| Object | marching band performances |
—
|
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: marching band performances | Statement: [Magic City Classic, hasHalftimeEvent, marching band performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHalftimeEvent Context triple: [Magic City Classic, hasHalftimeEvent, marching band performances]
-
A.
hasHalftime
Indicates that an event, typically a game or performance, includes a designated halftime interval between its main segments.
-
B.
halftimeShow
chosen
Indicates a performance or entertainment event that takes place during the intermission between two halves of a game or match.
-
C.
halftimeProducer
Indicates that one entity is the producer responsible for creating or organizing the halftime segment of an event, such as a sports game or show.
-
D.
halftimeScore
Indicates the score or result of a game or match at the halfway point (halftime).
-
E.
halftimeSponsor
Indicates a sponsorship relationship where an entity serves as the sponsor of the halftime segment of an event or performance.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.