Triple
T25491569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acharya |
E638848
|
entity |
| Predicate | featuresProtagonistBackground |
P39316
|
FINISHED |
| Object | former Naxalite |
—
|
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: former Naxalite | Statement: [Acharya, featuresProtagonistBackground, former Naxalite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProtagonistBackground Context triple: [Acharya, featuresProtagonistBackground, former Naxalite]
-
A.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
B.
hasProtagonistBackground
chosen
Indicates that a work or narrative features a specified background or origin story for its main protagonist.
-
C.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
D.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
protagonistField
Indicates that the subject is the main or central character (protagonist) within the specified narrative or context.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 21, 2026, 2:38 p.m.