Triple
T38440045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanooru Heggadithi |
E906461
|
entity |
| Predicate | authorOfSourceWorkFullName |
P166593
|
FINISHED |
| Object | Kuppali Venkatappa Puttappa |
—
|
NE NERFINISHED |
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: Kuppali Venkatappa Puttappa | Statement: [Kanooru Heggadithi, authorOfSourceWorkFullName, Kuppali Venkatappa Puttappa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfSourceWorkFullName Context triple: [Kanooru Heggadithi, authorOfSourceWorkFullName, Kuppali Venkatappa Puttappa]
-
A.
creatorFullName
Indicates the full personal name of the entity that created or authored another entity.
-
B.
authorOfParentWork
chosen
Indicates that one entity is the author of a work that serves as the parent or source for another related work.
-
C.
anonymousAuthorOfSourceWork
Indicates that a person is the (unidentified or unnamed) author of a given source work.
-
D.
composerOfSourceWork
Indicates that an entity is the composer who created the original source work on which another work is based.
-
E.
authorOfNamesakeWork
Indicates that an entity is the author or creator of a work that serves as the namesake for another entity (e.g., a person, place, or organization).
- F. None of above.
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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:31 p.m.