Triple
T6157954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puran Singh |
E137369
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Puran Singh |
E137369
|
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: Puran Singh | Statement: [Puran Singh, name, Puran Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Puran Singh Context triple: [Puran Singh, name, Puran Singh]
-
A.
Puran Singh
chosen
Puran Singh was a prominent Punjabi writer, poet, and thinker known for his influential contributions to modern Punjabi literature and spiritual-philosophical essays.
-
B.
Maha Singh
Maha Singh was a prominent Sikh chieftain of the Sukerchakia Misl and an important leader in late 18th-century Punjab, best known as the father of Maharaja Ranjit Singh.
-
C.
Jhujhar Singh
Jhujhar Singh was a 17th-century Bundela Rajput ruler of Orchha in central India, known for his conflicts with the Mughal Empire during Shah Jahan’s reign.
-
D.
Beant Singh
Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
-
E.
Man Singh
Man Singh was an Indian noble and close associate of Nana Sahib who played a role in the events of the 1857 Indian Rebellion.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d32ef548190bc215d052d3497fe |
completed | March 22, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c16edb92048190ba47571e28db3cb6 |
completed | March 23, 2026, 4:48 p.m. |
Created at: March 22, 2026, 4:17 p.m.