Triple
T30989326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar–Saudi Arabia relations |
E789622
|
entity |
| Predicate | borderDisputeSettled |
P126323
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Qatar–Saudi Arabia relations, borderDisputeSettled, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeSettled Context triple: [Qatar–Saudi Arabia relations, borderDisputeSettled, 1992]
-
A.
borderDisputeResolvedBy
chosen
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
B.
borderSettlement
Indicates that a settlement is located near or along a political or administrative border.
-
C.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
D.
borderDisputeRelatedLanguage
Indicates a relationship where the language is associated with, used in, or relevant to a border dispute between entities.
-
E.
borderDisputeNegotiationChannel
Indicates a communication or diplomatic channel used specifically for negotiating the resolution of a border dispute between parties.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: April 29, 2026, 8:56 p.m.