Triple
T7522137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishad Premji |
E177796
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Premji |
E31802
|
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: Premji | Statement: [Rishad Premji, familyName, Premji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Premji Context triple: [Rishad Premji, familyName, Premji]
-
A.
Premji
chosen
Premji is an Indian surname most prominently associated with billionaire philanthropist and Wipro chairman Azim Premji.
-
B.
Raja
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
-
C.
Sampati
Sampati is a character in the Indian epic Ramayana, a vulture-king known for being Jatayu’s elder brother who aids Rama’s allies by revealing Sita’s whereabouts.
-
D.
Pavanputra
Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
-
E.
Akrura
Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c3c4c08190ad418978afcc98ec |
completed | March 27, 2026, 9:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8462d743481909a3cfb6d31d94d98 |
completed | March 28, 2026, 9:20 p.m. |
Created at: March 27, 2026, 3:46 p.m.