Triple
T23720444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijapur district |
E586128
|
entity |
| Predicate | isInsurgencyAffected |
P153696
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bijapur district, isInsurgencyAffected, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInsurgencyAffected Context triple: [Bijapur district, isInsurgencyAffected, yes]
-
A.
endedInsurgencyType
Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
-
B.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
-
C.
effectOnInvasion
Indicates the influence or impact that one factor has on the occurrence, success, or intensity of an invasion.
-
D.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
E.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b910759c8190be189db3e86d7258 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7 p.m.