Triple
T25656426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak Valley |
E643248
|
entity |
| Predicate | linguisticConflict |
P18893
|
FINISHED |
| Object | Bengali–Assamese language tensions |
—
|
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: Bengali–Assamese language tensions | Statement: [Barak Valley, linguisticConflict, Bengali–Assamese language tensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticConflict Context triple: [Barak Valley, linguisticConflict, Bengali–Assamese language tensions]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictSpecific
chosen
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
C.
conflictForControlOf
Indicates a struggle or contest between parties to gain dominance, authority, or decision-making power over something.
-
D.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
E.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faebdbf08190ab8856d10be8abd1 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:33 p.m.