Triple
T36595868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Accords |
E902795
|
entity |
| Predicate | hasComponentAgreement |
—
|
GENERATED |
| Object | Tripartite Accord (Angola–Cuba–South Africa) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentAgreement Context triple: [New York Accords, hasComponentAgreement, Tripartite Accord (Angola–Cuba–South Africa)]
-
A.
hasAgreementSystem
Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
-
B.
hasCustomerAgreement
Indicates that a customer is bound by or associated with a specific agreement or contract.
-
C.
hasTypeOfAgreement
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
D.
implementsAgreementWith
Indicates that one party carries out or fulfills the terms of an agreement made with another party.
-
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. chosen
Provenance (1 batch)
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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.