Triple
T2542368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Rookie of the Year Award |
E57812
|
entity |
| Predicate | hasHadCoWinners |
P34452
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NBA Rookie of the Year Award, hasHadCoWinners, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHadCoWinners Context triple: [NBA Rookie of the Year Award, hasHadCoWinners, yes]
-
A.
hasMultipleWinnersPossible
chosen
Indicates that a situation, event, or contest allows for more than one winner to be recognized or selected.
-
B.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
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.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
E.
notableMultipleWinners
Indicates that the subject has achieved multiple wins or repeated successes in a notable event, competition, or award.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.