Triple
T30620131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi–Kuwaiti Neutral Zone |
E779422
|
entity |
| Predicate | partitionAgreementSigned |
P19828
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Saudi–Kuwaiti Neutral Zone, partitionAgreementSigned, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partitionAgreementSigned Context triple: [Saudi–Kuwaiti Neutral Zone, partitionAgreementSigned, 1965]
-
A.
agreementSigned
chosen
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
agencySignedWith
Indicates that a formal agreement or contract has been established between an agency and another party.
-
D.
signedAgreementName
Indicates that an entity has signed an agreement identified by a specific name.
-
E.
confirmedAgreementBetween
Indicates that a previously proposed agreement between two or more parties has been formally verified, accepted, and is now recognized as valid.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:27 p.m.