Triple
T32375730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roelf Meyer |
E827273
|
entity |
| Predicate | partnerInNegotiationsWith |
P378
|
FINISHED |
| Object | Cyril Ramaphosa |
—
|
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: Cyril Ramaphosa | Statement: [Roelf Meyer, partnerInNegotiationsWith, Cyril Ramaphosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInNegotiationsWith Context triple: [Roelf Meyer, partnerInNegotiationsWith, Cyril Ramaphosa]
-
A.
negotiatingParty
chosen
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
B.
negotiatesBetween
Indicates a relationship where an entity acts as an intermediary to facilitate negotiation or mediation between two other entities.
-
C.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
D.
partnerInConflictResolutionWith
Indicates that two entities collaborate as partners in resolving a specific conflict or dispute.
-
E.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 12:50 a.m.