Triple
T10803766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raj Chandra Bose |
E254909
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Raj |
E255793
|
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: Raj | Statement: [Raj Chandra Bose, givenName, Raj]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raj Context triple: [Raj Chandra Bose, givenName, Raj]
-
A.
Raj
chosen
Raj is the given name of Raj Reddy, a pioneering computer scientist known for his foundational work in artificial intelligence and robotics.
-
B.
Ravi
Ravi is a common Indian male given name of Sanskrit origin meaning "sun" or "sun god."
-
C.
Ravi
Ravi is one of the major rivers of northern India and Pakistan, flowing through the Punjab region and serving as an important tributary of the Indus River system.
-
D.
Ramji
Ramji is an Indian cinematographer known for his visually striking work in Tamil cinema, including the acclaimed film Paruthiveeran.
-
E.
Raja
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73370e7388190885b104fc883456e |
completed | April 9, 2026, 5:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de567a7ea0819088a2fa10f8367d89 |
completed | April 14, 2026, 3 p.m. |
Created at: April 8, 2026, 9:18 p.m.