Triple
T25454396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D. V. V. Danayya |
E637872
|
entity |
| Predicate | knownForCollaboration |
P60681
|
FINISHED |
| Object | Ram Charan |
—
|
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: Ram Charan | Statement: [D. V. V. Danayya, knownForCollaboration, Ram Charan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCollaboration Context triple: [D. V. V. Danayya, knownForCollaboration, Ram Charan]
-
A.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
B.
hasCollaboratedIn
chosen
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
knownForFeaturing
Indicates that one entity is notable or recognized for prominently including, presenting, or showcasing another entity.
-
E.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:04 p.m.