Triple
T10837286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raj Reddy |
E255793
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Reddy |
E255794
|
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: Reddy | Statement: [Raj Reddy, hasFamilyName, Reddy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reddy Context triple: [Raj Reddy, hasFamilyName, Reddy]
-
A.
Reddy
chosen
Reddy is a common Indian surname associated with various communities, notably in the states of Andhra Pradesh and Telangana.
-
B.
Sanjay Reddy
Sanjay Reddy is an Indian economist known for his work in development economics, poverty measurement, and global justice.
-
C.
Raghava
Raghava is an epithet of the Hindu deity Rama, highlighting his lineage from the Raghu dynasty and his role as a central hero of the Ramayana.
-
D.
Will Kuluva
Will Kuluva was an American character actor known for his numerous film and television roles from the 1940s through the 1970s.
-
E.
Ray Reddy
Ray Reddy is a supporting character in the film "Signs," known for his pivotal role in the tragic backstory that shapes the protagonist’s crisis of faith.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d746ff70148190b844ab92d796af6c |
completed | April 9, 2026, 6:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb12aae648190aa7c93cee60ae3ea |
completed | April 14, 2026, 9:27 p.m. |
Created at: April 8, 2026, 9:19 p.m.