Triple
T26149953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konidela family |
E659786
|
entity |
| Predicate | hasPoliticalFigure |
P173201
|
FINISHED |
| Object | Chiranjeevi |
—
|
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: Chiranjeevi | Statement: [Konidela family, hasPoliticalFigure, Chiranjeevi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalFigure Context triple: [Konidela family, hasPoliticalFigure, Chiranjeevi]
-
A.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
B.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
C.
hasPoliticalPositionOn
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
-
D.
hasNotablePoliticalRoleIn
Indicates that an entity holds or has held a significant political position, function, or influence within a specified context or jurisdiction.
-
E.
notablePolitician
Indicates that the subject is a politician who is recognized as notable or significant in a political context.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 26, 2026, 8:24 p.m.