Triple
T29372725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandler Jones |
E744894
|
entity |
| Predicate | passRushSpecialty |
P42001
|
FINISHED |
| Object | edge rusher |
—
|
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: edge rusher | Statement: [Chandler Jones, passRushSpecialty, edge rusher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passRushSpecialty Context triple: [Chandler Jones, passRushSpecialty, edge rusher]
-
A.
passRusher
chosen
Indicates that an entity performs the role or action of rushing the passer, typically attempting to pressure or sack the quarterback.
-
B.
runningBack
Indicates that one entity is acting as a running back in relation to another entity, typically within the context of an American football play or team.
-
C.
rushingYards
Indicates the number of yards a player gains by running the ball on rushing plays.
-
D.
careerRushingYards
Indicates the total number of rushing yards an entity has accumulated over the entire span of its career.
-
E.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669abeb9c8190b783abe525e9ad32 |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:28 p.m.