Triple
T33233816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mud Bowl |
E850772
|
entity |
| Predicate | JetsOffensePerformance |
P111358
|
FINISHED |
| Object | shut out |
—
|
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: shut out | Statement: [The Mud Bowl, JetsOffensePerformance, shut out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JetsOffensePerformance Context triple: [The Mud Bowl, JetsOffensePerformance, shut out]
-
A.
JetsScore
Indicates that the team named Jets scores a certain number of points in a game or event.
-
B.
offensiveStrength
chosen
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
-
C.
ABAFieldGoalPercentageLeader
Indicates the player who led the ABA in field goal percentage for a given season or time period.
-
D.
offensiveSchemeRunnerUp
Indicates that an offensive scheme finished in second place or was the runner-up in a particular ranking, contest, or evaluation.
-
E.
offensivePlayType
Indicates the specific type of offensive play that is being executed or has occurred within a game or sporting context.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.