Triple
T9446775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigray War |
E227783
|
entity |
| Predicate | serviceDisruption |
P7316
|
FINISHED |
| Object | banking services cut off 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: banking services cut off in Tigray | Statement: [Tigray War, serviceDisruption, banking services cut off in Tigray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceDisruption Context triple: [Tigray War, serviceDisruption, banking services cut off in Tigray]
-
A.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
B.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
C.
disruptsContinuityOf
chosen
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
D.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
E.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction of another entity.
- 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.