Triple
T35317336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl LIX halftime show |
E1019938
|
entity |
| Predicate | expectedFeature |
P181483
|
FINISHED |
| Object | multiple musical acts |
—
|
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: multiple musical acts | Statement: [Super Bowl LIX halftime show, expectedFeature, multiple musical acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedFeature Context triple: [Super Bowl LIX halftime show, expectedFeature, multiple musical acts]
-
A.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
-
B.
expectedAction
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
-
C.
promisedFeature
Indicates that one entity has committed to providing or implementing a specific feature for another entity.
-
D.
expectedContent
chosen
Indicates that a particular entity is anticipated or required to contain or include specific content.
-
E.
plannedFeature
Indicates that a particular feature is intended or scheduled to be developed or implemented in the future.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790929a888190aa7084a792c304fc |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.