Triple
T30989350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar–Saudi Arabia relations |
E789622
|
entity |
| Predicate | reconciliationAgreement |
P68025
|
FINISHED |
| Object | Al-Ula Declaration |
—
|
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: Al-Ula Declaration | Statement: [Qatar–Saudi Arabia relations, reconciliationAgreement, Al-Ula Declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconciliationAgreement Context triple: [Qatar–Saudi Arabia relations, reconciliationAgreement, Al-Ula Declaration]
-
A.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
B.
subsequentAgreement
Indicates that a later agreement or understanding was reached that follows and potentially modifies or supplements an earlier one.
-
C.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
D.
confirmedAgreementBetween
Indicates that a previously proposed agreement between two or more parties has been formally verified, accepted, and is now recognized as valid.
-
E.
involvedAgreement
chosen
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.