Triple
T16842435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nish Kumar |
E409445
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kumar |
E870145
|
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: Kumar | Statement: [Nish Kumar, familyName, Kumar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumar Context triple: [Nish Kumar, familyName, Kumar]
-
A.
Kumar
chosen
Kumar is a common Indian surname and given name used across various regions and communities in South Asia.
-
B.
Kunal Khemu
Kunal Khemu is an Indian film actor who began his career as a popular child artist in the 1990s and later gained recognition for his roles in Hindi comedies and dramas.
-
C.
Arun
Arun is a local government district and borough in West Sussex, England, named after the River Arun and encompassing coastal towns such as Bognor Regis and Littlehampton.
-
D.
Arun
Arun is a masculine given name commonly used in South Asian cultures, often associated with the sun or dawn.
-
E.
Gautam Kumar
Gautam Kumar is known as the son of legendary Indian Bengali actor Uttam Kumar.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35167a48190b45a459023e3ab1b |
completed | April 18, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb199168819080a9ddc7534f19a7 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.