Triple
T33199724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amar Varma |
E849865
|
entity |
| Predicate | storyBackdrop |
P175305
|
FINISHED |
| Object | insurgency in Northeast India |
—
|
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: insurgency in Northeast India | Statement: [Amar Varma, storyBackdrop, insurgency in Northeast India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyBackdrop Context triple: [Amar Varma, storyBackdrop, insurgency in Northeast India]
-
A.
politicalBackdropFor
chosen
Indicates that one situation, event, or context serves as the political background or setting within which another event or relationship occurs or is interpreted.
-
B.
musicalBackdrop
Indicates that one entity serves as the background music or ambient sound accompanying another entity or event.
-
C.
primaryBackdropFor
Indicates that one entity serves as the main visual or contextual background element for another entity.
-
D.
stageImage
Indicates that an image is being prepared, arranged, or set up for display or presentation in a particular context or environment.
-
E.
typicalBackground
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:29 a.m.