Triple
T877551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian coalition governments |
E18955
|
entity |
| Predicate | conflictManagementMechanism |
P21013
|
FINISHED |
| Object | coalition coordination councils |
—
|
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: coalition coordination councils | Statement: [Norwegian coalition governments, conflictManagementMechanism, coalition coordination councils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictManagementMechanism Context triple: [Norwegian coalition governments, conflictManagementMechanism, coalition coordination councils]
-
A.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb06ea88190962502172d434eb4 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.