Triple
T31743208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nambala Keshava Rao |
E810193
|
entity |
| Predicate | hasBountyOnHead |
P192846
|
FINISHED |
| Object | multi-million rupee cash reward |
—
|
LITERAL 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: multi-million rupee cash reward | Statement: [Nambala Keshava Rao, hasBountyOnHead, multi-million rupee cash reward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBountyOnHead Context triple: [Nambala Keshava Rao, hasBountyOnHead, multi-million rupee cash reward]
-
A.
hasCasque
Indicates that one entity possesses, wears, or is equipped with a casque (a type of helmet or protective headgear).
-
B.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
C.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
D.
hasSkull
Indicates that an entity possesses or is characterized by the presence of a skull.
-
E.
hasHeadNear
Indicates that one entity’s head is positioned close to another entity or reference point in space.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: April 30, 2026, 11:25 p.m.