Triple
T8573441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haason Reddick |
E202984
|
entity |
| Predicate | playsDefensiveRole |
P13143
|
FINISHED |
| Object | outside linebacker |
—
|
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: outside linebacker | Statement: [Haason Reddick, playsDefensiveRole, outside linebacker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsDefensiveRole Context triple: [Haason Reddick, playsDefensiveRole, outside linebacker]
-
A.
defensiveRole
chosen
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
B.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
-
C.
decisiveDefensivePlayer
Indicates a defensive player whose actions are crucial in determining the outcome of defensive plays or key moments in a game.
-
D.
playsRoleInOffense
Indicates that an entity performs a specific function or position within an offensive strategy or system.
-
E.
defensiveTackle
Indicates that an entity plays the defensive tackle position, typically lining up on the interior of the defensive line to disrupt offensive plays.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea458c1081908e79bee2cbf97207 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.