Triple
T36596266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luena |
E902807
|
entity |
| Predicate | countryConflict |
P71384
|
FINISHED |
| Object | Angolan Civil War |
E46009
|
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: Angolan Civil War | Statement: [Luena, countryConflict, Angolan Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryConflict Context triple: [Luena, countryConflict, Angolan Civil War]
-
A.
conflictCountry
chosen
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
B.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
-
C.
politicalConflict
Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
-
D.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
E.
contemporaryConflict
Indicates a conflict or dispute occurring between entities within the same general time period or historical era.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a03173dd4988190a38175b63cba9f09 |
completed | May 12, 2026, 12:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f920a1dc8190b765d4c5e31df67a |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a031700ade88190afd217d5966b03b4 |
completed | May 12, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:11 p.m.