Triple
T11022916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamal Bose |
E260534
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Anand |
E365453
|
NE 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: Anand | Statement: [Kamal Bose, notableWork, Anand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anand Context triple: [Kamal Bose, notableWork, Anand]
-
A.
Anand
chosen
Anand is a city in the Indian state of Gujarat, known as a major dairy hub and home to the Amul cooperative.
-
B.
Viswanathan Anand
Viswanathan Anand is an Indian chess grandmaster and former World Chess Champion widely regarded as one of the greatest chess players of all time.
-
C.
Viswanathan
Viswanathan is the given name of Viswanathan Anand, the Indian chess grandmaster and former World Chess Champion.
-
D.
Nihal
Nihal is a bright yellow giant star in the constellation Lepus, notable as one of its most luminous members.
-
E.
Vishy
Vishy is the popular nickname of Viswanathan Anand, the Indian chess grandmaster and former World Chess Champion renowned for his rapid playing style and contributions to modern chess.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bd88188190a644adc9283cabb8 |
completed | April 9, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3750917d481909e73de0bfae27827 |
completed | April 18, 2026, 12:11 p.m. |
Created at: April 8, 2026, 9:25 p.m.