Triple
T33233815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mud Bowl |
E850772
|
entity |
| Predicate | defensiveHighlight |
P82243
|
FINISHED |
| Object | multiple interceptions by Miami defense |
—
|
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 interceptions by Miami defense | Statement: [The Mud Bowl, defensiveHighlight, multiple interceptions by Miami defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveHighlight Context triple: [The Mud Bowl, defensiveHighlight, multiple interceptions by Miami defense]
-
A.
defensiveSuccess
chosen
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
B.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
-
C.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
-
D.
defensivePlayerInvolved
Indicates that a defensive player participates in or is directly involved in a particular play, event, or defensive action.
-
E.
defensiveLeader
Indicates that an entity serves as the primary organizer or coordinator of defensive actions or strategies for another entity or group.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:31 a.m.