Triple
T36346659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Payton Award |
E895082
|
entity |
| Predicate | typeOfPlayerRecognized |
P199298
|
FINISHED |
| Object | quarterbacks |
—
|
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: quarterbacks | Statement: [Walter Payton Award, typeOfPlayerRecognized, quarterbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPlayerRecognized Context triple: [Walter Payton Award, typeOfPlayerRecognized, quarterbacks]
-
A.
playerRecognitionType
Indicates the type or manner in which a player is acknowledged, identified, or recognized within a given context or system.
-
B.
hasTypeOfPlayers
chosen
Indicates that an entity is associated with a specific category or kind of players involved in it.
-
C.
formerPlayerType
Indicates that an entity previously had a specific player role or classification but no longer holds that status.
-
D.
sportingRoleRecognised
Indicates that a particular sporting role or position has been formally acknowledged or accepted as valid within a given context or system.
-
E.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:09 p.m.