Triple
T31429830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys 1990s Super Bowl dynasty |
E801764
|
entity |
| Predicate | starWideReceiver |
P171861
|
FINISHED |
| Object | Michael Irvin |
—
|
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: Michael Irvin | Statement: [Dallas Cowboys 1990s Super Bowl dynasty, starWideReceiver, Michael Irvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starWideReceiver Context triple: [Dallas Cowboys 1990s Super Bowl dynasty, starWideReceiver, Michael Irvin]
-
A.
startingWideReceiver
Indicates that the specified player is designated as a starting wide receiver for a team in a game or season.
-
B.
DenverBroncosWideReceiver
Indicates that an entity is a wide receiver who plays (or played) for the Denver Broncos football team.
-
C.
oregonStateWideReceiver
Indicates a relationship where an entity serves as a wide receiver for the Oregon State football team.
-
D.
touchdownReceptionLeaderForTeam
Indicates the player who has recorded the most touchdown receptions for a given team.
-
E.
roleAtTampaBayBuccaneers
Indicates that an entity holds or held a specific role or position within the Tampa Bay Buccaneers organization.
- 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_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. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:56 p.m.