Triple
T36033936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dustin Hazelett |
E1042345
|
entity |
| Predicate | earnedBonusAward |
P113458
|
FINISHED |
| Object | Submission of the Night |
—
|
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: Submission of the Night | Statement: [Dustin Hazelett, earnedBonusAward, Submission of the Night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedBonusAward Context triple: [Dustin Hazelett, earnedBonusAward, Submission of the Night]
-
A.
bonusCategory
Indicates the classification or type of bonus associated with an entity or transaction.
-
B.
awardCurrency
Indicates that one entity grants or gives a specified amount of currency to another entity.
-
C.
awardEffect
chosen
Indicates that one entity confers or grants a benefit, recognition, or reward that has a particular impact or consequence on another entity.
-
D.
returnedAward
Indicates that an entity has given back or relinquished a previously received award to the awarding party or institution.
-
E.
goalAwarded
Indicates that a specific goal or objective has been granted or conferred upon an entity as an award or achievement.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad190ac48190b8dd2eb2356c2d45 |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.