Triple
T21152594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mistahimaskwa |
E521228
|
entity |
| Predicate | stanceDuringConflict |
P143081
|
FINISHED |
| Object | reluctant to engage in armed conflict |
—
|
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: reluctant to engage in armed conflict | Statement: [Mistahimaskwa, stanceDuringConflict, reluctant to engage in armed conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceDuringConflict Context triple: [Mistahimaskwa, stanceDuringConflict, reluctant to engage in armed conflict]
-
A.
heldDuringConflict
Indicates that an entity maintained control, possession, or occupation of something for some duration while an identified conflict was ongoing.
-
B.
significantDuringConflict
Indicates that something plays an important or influential role specifically in the context of a conflict or dispute.
-
C.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
D.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
E.
reignDuringConflict
Indicates that a ruler’s period of reign overlaps in time with a specified conflict or war.
- F. None of above. chosen
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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7240275b481908748c0e3f187ed34 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.