Triple
T11923256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zora Singh |
E283712
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Singh |
E94257
|
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: Singh | Statement: [Zora Singh, familyName, Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Singh Context triple: [Zora Singh, familyName, Singh]
-
A.
Singh
chosen
Singh is a common Indian surname used across various regions and communities, often associated with warriors, nobility, and particularly with Sikh and Rajput heritage.
-
B.
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.
-
C.
Balbir
Balbir is the given first name of the Indian actor and film producer Shashi Kapoor.
-
D.
Suchat Singh
Suchat Singh was a historical figure associated with the construction and patronage of Hindu religious architecture in India.
-
E.
Akali Phula Singh
Akali Phula Singh was a prominent Sikh warrior-monk and military leader renowned for his bravery and key role in expanding and defending the Sikh Empire in the early 19th century.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e2fc648190a446c1917db1c7d9 |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f44042cf1c81909de44acfe1202482 |
completed | May 1, 2026, 5:55 a.m. |
Created at: April 8, 2026, 9:45 p.m.