Triple
T16298679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 669 |
E395718
|
entity |
| Predicate | invasionAddressed |
P122586
|
FINISHED |
| Object | Iraq’s invasion of Kuwait |
—
|
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: Iraq’s invasion of Kuwait | Statement: [UN Security Council Resolution 669, invasionAddressed, Iraq’s invasion of Kuwait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasionAddressed Context triple: [UN Security Council Resolution 669, invasionAddressed, Iraq’s invasion of Kuwait]
-
A.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
B.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
C.
effectOnInvasion
Indicates the influence or impact that one factor has on the occurrence, success, or intensity of an invasion.
-
D.
plannedInvasionOf
Indicates that one entity has formulated or organized an invasion targeting another entity.
-
E.
methodOfInvasion
Indicates the specific way or technique by which an invasion is carried out.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e30ee288190b78807b60cb18e22 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.