Triple
T105010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf War |
E2119
|
entity |
| Predicate | IraqiAction |
P1549
|
FINISHED |
| Object | burning Kuwaiti oil wells |
—
|
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: burning Kuwaiti oil wells | Statement: [Gulf War, IraqiAction, burning Kuwaiti oil wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IraqiAction Context triple: [Gulf War, IraqiAction, burning Kuwaiti oil wells]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
-
C.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
D.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
E.
associatedWithWar
chosen
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.