Triple
T24802355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antwaan Randle El |
E620558
|
entity |
| Predicate | touchdownPassRecipientInSuperBowlXL |
P157147
|
FINISHED |
| Object | Hines Ward |
—
|
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: Hines Ward | Statement: [Antwaan Randle El, touchdownPassRecipientInSuperBowlXL, Hines Ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touchdownPassRecipientInSuperBowlXL Context triple: [Antwaan Randle El, touchdownPassRecipientInSuperBowlXL, Hines Ward]
-
A.
roleInSuperBowlXLV
Indicates the specific role or capacity an entity had in relation to Super Bowl XLV.
-
B.
SuperBowlChampionAsPlayerWith
Indicates that one entity was a Super Bowl champion as a player in association with the other entity (such as a team, season, or organization).
-
C.
appearedInSuperBowl
Indicates that the entity participated as a player, coach, or key contributor in at least one Super Bowl game.
-
D.
MVPOfSuperBowl
Indicates that the subject was selected as the Most Valuable Player (MVP) of the specified Super Bowl game.
-
E.
touchdownReceptionLeaderForTeam
Indicates the player who has recorded the most touchdown receptions for a given team.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412ab84288190b9c43aafc773c5bc |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:49 a.m.