Triple
T31429829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys 1990s Super Bowl dynasty |
E801764
|
entity |
| Predicate | starRunningBack |
P36657
|
FINISHED |
| Object | Emmitt Smith |
—
|
NE NERFINISHED |
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: Emmitt Smith | Statement: [Dallas Cowboys 1990s Super Bowl dynasty, starRunningBack, Emmitt Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starRunningBack Context triple: [Dallas Cowboys 1990s Super Bowl dynasty, starRunningBack, Emmitt Smith]
-
A.
runningBack
chosen
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.
-
B.
numberOfRunningBacks
Indicates the quantity of running backs involved or associated in the given context or situation.
-
C.
passRusher
Indicates that an entity performs the role or action of rushing the passer, typically attempting to pressure or sack the quarterback.
-
D.
runningBackInFilm
Indicates that an entity serves as the running back character or role within a particular film.
-
E.
runningBackGiants
Indicates that the subject is a running back who plays for the New York Giants football team.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:56 p.m.