Triple
T29668970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Sports Awards in India |
E750612
|
entity |
| Predicate | DhyanChandAwardEstablished |
P144003
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [National Sports Awards in India, DhyanChandAwardEstablished, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DhyanChandAwardEstablished Context triple: [National Sports Awards in India, DhyanChandAwardEstablished, 2002]
-
A.
hasIndianLaureate
Indicates that an entity has at least one laureate who is of Indian nationality or origin.
-
B.
firstClassAwardedTo
Indicates that a first-class distinction, honor, or top-level award is given to a particular recipient.
-
C.
numberOfRailwayCupMedals
Indicates the count of Railway Cup medals associated with a given entity.
-
D.
awardEstablishedFor
chosen
Indicates that an award was created or instituted specifically to recognize or honor a particular purpose, achievement, or category.
-
E.
nationalPlayerOfTheYearAward
Indicates that an athlete has been selected as the top national player of the year in their sport or league.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f671c5d3308190b78b458b37ee5e47 |
completed | May 2, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:03 p.m.