Triple
T27282703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yemenite War of 1979 |
E688380
|
entity |
| Predicate | ceasefireBrokeredIn |
P26557
|
FINISHED |
| Object | Kuwait City |
—
|
NE NERFINISHED |
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: Kuwait City | Statement: [Yemenite War of 1979, ceasefireBrokeredIn, Kuwait City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasefireBrokeredIn Context triple: [Yemenite War of 1979, ceasefireBrokeredIn, Kuwait City]
-
A.
ceasefireBrokeredBy
Indicates that a ceasefire agreement was arranged or facilitated through the mediation efforts of a specific party or entity.
-
B.
ceasefireBroker
chosen
Indicates that an entity mediates and facilitates an agreement to stop hostilities between conflicting parties.
-
C.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
D.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
E.
ceasefireWith
Indicates a mutual agreement between parties to stop hostilities or armed conflict, typically for a specified period or under certain conditions.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6275281288190baf993960cf87fac |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:09 a.m.