Triple
T105013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf War |
E2119
|
entity |
| Predicate | coalitionObjective |
P4658
|
FINISHED |
| Object | expel Iraqi forces from 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: expel Iraqi forces from Kuwait | Statement: [Gulf War, coalitionObjective, expel Iraqi forces from Kuwait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionObjective Context triple: [Gulf War, coalitionObjective, expel Iraqi forces from Kuwait]
-
A.
politicalGoal
chosen
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
B.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
C.
objectiveOfUnitedStates
Indicates that something is an official objective or goal pursued by the United States.
-
D.
nationalCommittee
Indicates that an entity serves as or is associated with a national-level committee or governing body for another entity.
-
E.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
- 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.