Triple
T29786756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asante |
E756284
|
entity |
| Predicate | engagedInConflictType |
P1397
|
FINISHED |
| Object | Anglo-Ashanti Wars |
—
|
NE NERFINISHED |
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: Anglo-Ashanti Wars | Statement: [Asante, engagedInConflictType, Anglo-Ashanti Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagedInConflictType Context triple: [Asante, engagedInConflictType, Anglo-Ashanti Wars]
-
A.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
B.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
E.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674abd4bc81908993a7677238b80c |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:09 p.m.