Triple
T31649368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Turner |
E807674
|
entity |
| Predicate | rushingStyle |
P65104
|
FINISHED |
| Object | between-the-tackles power running |
—
|
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: between-the-tackles power running | Statement: [Michael Turner, rushingStyle, between-the-tackles power running]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushingStyle Context triple: [Michael Turner, rushingStyle, between-the-tackles power running]
-
A.
passRusher
Indicates that an entity performs the role or action of rushing the passer, typically attempting to pressure or sack the quarterback.
-
B.
runningStyle
chosen
Indicates the characteristic manner or form in which an entity performs running.
-
C.
rushingYards
Indicates the number of yards a player gains by running the ball on rushing plays.
-
D.
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.
-
E.
rushType
Indicates the kind or category of urgency associated with an action, request, or process.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a95865088190b6c1649a11651edb |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:52 p.m.