Triple
T5183738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Offensive Rookie of the Year |
E116980
|
entity |
| Predicate | hasMultipleWinnersPerYear |
P34452
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [NFL Offensive Rookie of the Year, hasMultipleWinnersPerYear, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleWinnersPerYear Context triple: [NFL Offensive Rookie of the Year, hasMultipleWinnersPerYear, no]
-
A.
hasMultipleMedalsPerYear
Indicates that an entity has been awarded more than one medal within the same calendar year.
-
B.
hasMultipleWinnersPossible
chosen
Indicates that a situation, event, or contest allows for more than one winner to be recognized or selected.
-
C.
hasMultipleWinnersPerPositionInLeague
Indicates that, within a given league, a single position can be held or won by more than one winner simultaneously or in the same season.
-
D.
notableMultipleWinners
Indicates that the subject has achieved multiple wins or repeated successes in a notable event, competition, or award.
-
E.
maximumNumberOfLaureatesPerYear
Indicates the highest allowable or observed count of laureates associated with a given year.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799eb90c8190b738e9478699180f |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.