Triple
T7374197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assab Port |
E170082
|
entity |
| Predicate | conflictImpact |
P57235
|
FINISHED |
| Object | operations affected by Eritrean–Ethiopian War |
—
|
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: operations affected by Eritrean–Ethiopian War | Statement: [Assab Port, conflictImpact, operations affected by Eritrean–Ethiopian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictImpact Context triple: [Assab Port, conflictImpact, operations affected by Eritrean–Ethiopian War]
-
A.
associatedConflictImpact
chosen
Indicates a relationship where an entity is linked to a specific conflict and the effects or consequences that conflict has on it.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
D.
settingOfConflict
Indicates the location or context in which a conflict between entities takes place.
-
E.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a6643c81909d626c8b6a7a11fd |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.