Triple
T22754267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tendulkar |
E562795
|
entity |
| Predicate | notableBearer |
P458
|
FINISHED |
| Object | Sachin Tendulkar |
—
|
NE NERFINISHED |
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: Sachin Tendulkar | Statement: [Tendulkar, notableBearer, Sachin Tendulkar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sachin Tendulkar Context triple: [Tendulkar, notableBearer, Sachin Tendulkar]
-
A.
Sachin Tendulkar
chosen
Sachin Tendulkar is a legendary Indian cricketer widely regarded as one of the greatest batsmen in the history of the sport.
-
B.
Tendulkar
Tendulkar is a prominent Indian surname most famously associated with legendary cricketer Sachin Tendulkar and his family.
-
C.
Sachin
Sachin is a producer known for his work associated with the project or entity "Astitva."
-
D.
Sachin
Sachin is an industrial suburb located within the Surat metropolitan region in the Indian state of Gujarat.
-
E.
Sunil Gavaskar
Sunil Gavaskar is a legendary Indian opening batsman widely regarded as one of the greatest cricketers of all time, renowned for his prolific Test run-scoring and record-breaking centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bb80ac8190b53a1e00704c4ff5 |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:25 p.m.