Triple
T16919631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B. D. Sharma |
E410410
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Sharma |
E569129
|
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: Sharma | Statement: [B. D. Sharma, hasFamilyName, Sharma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sharma Context triple: [B. D. Sharma, hasFamilyName, Sharma]
-
A.
Sharma
chosen
Sharma is a common Indian surname found across various regions and communities, particularly among those of Brahmin heritage.
-
B.
Shashi
Shashi is an Indian given name commonly used for both males and females, often associated with the moon or moonlight in Sanskrit.
-
C.
Shyam
Shyam is the young protagonist of the classic Marathi autobiographical novel "Shyamchi Aai," depicting his deep bond with his mother and his moral and emotional growth.
-
D.
Sinha
Sinha is an Indian surname commonly found among people of various communities, particularly in the northern and eastern regions of India.
-
E.
Sinha
Sinha is a component or constituent part associated with the larger entity known as Sri Raja Sinha.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c7c2c9cc8190b6d59d0a8edd078d |
completed | May 10, 2026, 6 p.m. |
Created at: April 10, 2026, 5:30 a.m.