Triple
T16428719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.K. Metcalf |
E399013
|
entity |
| Predicate | 40YardDashTime |
P122746
|
FINISHED |
| Object | about 4.33 seconds |
—
|
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: about 4.33 seconds | Statement: [D.K. Metcalf, 40YardDashTime, about 4.33 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 40YardDashTime Context triple: [D.K. Metcalf, 40YardDashTime, about 4.33 seconds]
-
A.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
-
B.
legRunner
Indicates that an entity functions as a runner or moving component that operates in conjunction with a leg or leg-like structure.
-
C.
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.
-
D.
rushingYards
Indicates the number of yards a player gains by running the ball on rushing plays.
-
E.
passRusher
Indicates that an entity performs the role or action of rushing the passer, typically attempting to pressure or sack the quarterback.
- F. None of above. chosen
Provenance (4 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fd49708190abb5065fa430eff1 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.