Triple
T9446774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigray War |
E227783
|
entity |
| Predicate | communicationImpact |
P4312
|
FINISHED |
| Object | communications blackout in Tigray |
—
|
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: communications blackout in Tigray | Statement: [Tigray War, communicationImpact, communications blackout in Tigray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationImpact Context triple: [Tigray War, communicationImpact, communications blackout in Tigray]
-
A.
encodingImpact
Indicates how one encoding or encoding choice affects, modifies, or constrains another process, representation, or outcome.
-
B.
workImpact
Indicates that one entity’s work has an effect or influence on another entity, situation, or outcome.
-
C.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
D.
socialImpact
chosen
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
E.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f35394c8190aa77528dabd6139c |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.