Triple
T31225101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi territorial waters |
E796115
|
entity |
| Predicate | disputeHistoryWith |
P3572
|
FINISHED |
| Object | Kuwait |
—
|
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 | Statement: [Iraqi territorial waters, disputeHistoryWith, Kuwait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeHistoryWith Context triple: [Iraqi territorial waters, disputeHistoryWith, Kuwait]
-
A.
hasDisputeHistory
chosen
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
disputeStatus
Indicates the current state or condition of a disagreement or conflict between parties.
-
D.
disputeIssue
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
E.
disputeNumber
Indicates the identifier or count associated with a specific dispute within a set of disputes.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c5030b88190bac4667e104238af |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.