Triple
T16087789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Sinha |
E390276
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sinha |
E1119270
|
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: Sinha | Statement: [Lord Sinha, familyName, Sinha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sinha Context triple: [Lord Sinha, familyName, Sinha]
-
A.
Sinha
Sinha is a component or constituent part associated with the larger entity known as Sri Raja Sinha.
-
B.
Sinha
chosen
Sinha is an Indian surname commonly found among people of various communities, particularly in the northern and eastern regions of India.
-
C.
Sahoo
Sahoo is an Indian surname, particularly common in eastern India, associated with various communities and often linked to mercantile or administrative occupations.
-
D.
Sanjay
Sanjay is the given name of Sanjay Gandhi, an influential and controversial Indian politician and son of former Prime Minister Indira Gandhi.
-
E.
Sanjeev
Sanjeev is a central character in Jhumpa Lahiri’s short story “This Blessed House,” portrayed as a practical, traditional Indian-American husband struggling to reconcile his values with his free-spirited wife’s quirks.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e184508dfc819085590b2c4731c8ef |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe490d494819081f812811f032702 |
completed | May 10, 2026, 1:51 a.m. |
Created at: April 10, 2026, 4:59 a.m.