Triple
T31743204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nambala Keshava Rao |
E810193
|
entity |
| Predicate | joinedMovement |
P2459
|
FINISHED |
| Object | Naxalite movement in Srikakulam region |
—
|
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: Naxalite movement in Srikakulam region | Statement: [Nambala Keshava Rao, joinedMovement, Naxalite movement in Srikakulam region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedMovement Context triple: [Nambala Keshava Rao, joinedMovement, Naxalite movement in Srikakulam region]
-
A.
joinedShu
Indicates that an entity became a member or ally of the group or faction named Shu.
-
B.
associatedWithMovement
chosen
Indicates a relationship where an entity is connected to, involved in, or influenced by a particular movement (e.g., social, political, artistic, or ideological).
-
C.
joinMethod
Indicates the technique or approach by which two or more entities are combined or linked together.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movementFounded
Indicates that an entity established or initiated the creation of a movement.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:25 p.m.