Triple
T36687215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendre Naadige Ondu Gite |
E905849
|
entity |
| Predicate | literaryTributeTo |
P191127
|
FINISHED |
| Object | D. R. Bendre |
—
|
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: D. R. Bendre | Statement: [Bendre Naadige Ondu Gite, literaryTributeTo, D. R. Bendre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryTributeTo Context triple: [Bendre Naadige Ondu Gite, literaryTributeTo, D. R. Bendre]
-
A.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other entity.
-
B.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
C.
literaryMuseOf
Indicates a relationship in which one entity serves as the creative inspiration or muse for another entity’s literary work.
-
D.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
E.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
- F. None of above. chosen
Provenance (4 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 3, 2026, 4:12 p.m.