Triple
T17222985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nau Nihal Singh |
E418034
|
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: [Nau Nihal Singh, familyName, Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Singh Context triple: [Nau Nihal 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.
Sangram Singh
Sangram Singh, better known as Rana Sanga, was a prominent 16th-century Rajput king of Mewar renowned for his resistance against the Mughal emperor Babur and other invading forces in northern India.
-
C.
Sinha
Sinha is a component or constituent part associated with the larger entity known as Sri Raja Sinha.
-
D.
Sinha
Sinha is an Indian surname commonly found among people of various communities, particularly in the northern and eastern regions of India.
-
E.
Shaan Singh
Shaan Singh is a musician best known as a member of the band The Hooligans.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddf2c3c8190b6adceaaefd4ccbf |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0167596ab481909df59ce68c7f640e |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:38 a.m.