Triple
T14271529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rao |
E353796
|
entity |
| Predicate | relatedTitle |
P914
|
FINISHED |
| Object | Thakur |
E120913
|
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: Thakur | Statement: [Rao, relatedTitle, Thakur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thakur Context triple: [Rao, relatedTitle, Thakur]
-
A.
Thakur
chosen
Thakur is a traditional Indian feudal and honorific title historically used by landowning nobility and warrior elites, particularly among Rajput communities.
-
B.
Ransingha
Ransingha is a traditional curved brass or copper trumpet used in Himalayan folk music, especially in ceremonial and ritual contexts.
-
C.
Prithi Chand
Prithi Chand was the eldest son of the fourth Sikh Guru, Guru Ram Das, known for later opposing the succession of his younger brother Guru Arjan and founding a rival sect.
-
D.
Gobind
Gobind is the given name of Guru Gobind Singh, the tenth Sikh Guru and a central figure in Sikh history.
-
E.
Atal Rai
Atal Rai was a revered Sikh figure remembered as the young son of the sixth Sikh Guru, Guru Hargobind, and is honored for his spiritual devotion and early death.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de65811d7c8190b075909a6570d415 |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd326a5aec8190b139a0c49fd43705 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:10 a.m.