Triple
T36595868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Accords |
E902795
|
entity |
| Predicate | hasComponentAgreement |
P204953
|
FINISHED |
| Object | Tripartite Accord (Angola–Cuba–South Africa) |
E902796
|
NE 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: Tripartite Accord (Angola–Cuba–South Africa) | Statement: [New York Accords, hasComponentAgreement, Tripartite Accord (Angola–Cuba–South Africa)]
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 (5 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f922bfe48190a9f67a6f5cb07cc7 |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.