Triple
T24831988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 65 |
E621363
|
entity |
| Predicate | isPostConflictInstrument |
P157388
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United Nations Security Council Resolution 65, isPostConflictInstrument, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPostConflictInstrument Context triple: [United Nations Security Council Resolution 65, isPostConflictInstrument, true]
-
A.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
B.
conflictsOccurIn
Indicates that one or more conflicts take place within, or are situated in, a specified context, location, or setting.
-
C.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
-
D.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
-
E.
postConflictStatus
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:15 a.m.