Triple
T11634642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Rookie of the Month awards |
E276484
|
entity |
| Predicate | winnerSelection |
P52161
|
FINISHED |
| Object | conference-based |
—
|
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: conference-based | Statement: [NBA Rookie of the Month awards, winnerSelection, conference-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerSelection Context triple: [NBA Rookie of the Month awards, winnerSelection, conference-based]
-
A.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
B.
winnerType
chosen
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
winnerRight
Indicates that the referenced entity is the winner on the right side or right position in a competitive or comparative context.
-
E.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25c0b00819095898d2b2445ecfb |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.