Triple
T31451231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islam in Ethiopia |
E802324
|
entity |
| Predicate | hasConflictHistoryWith |
P37642
|
FINISHED |
| Object | Christian Ethiopian empires |
E61656
|
NE 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: Christian Ethiopian empires | Statement: [Islam in Ethiopia, hasConflictHistoryWith, Christian Ethiopian empires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConflictHistoryWith Context triple: [Islam in Ethiopia, hasConflictHistoryWith, Christian Ethiopian empires]
-
A.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
B.
conflictedOverBy
Indicates that one entity is the subject of conflict, dispute, or contention initiated or experienced by another entity.
-
C.
conflictHistory
chosen
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
D.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
E.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
- F. None of above.
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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b078863d481908b6855846faef412 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: April 30, 2026, 9:13 p.m.