Triple
T282527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reagan–Gorbachev summits |
E5382
|
entity |
| Predicate | typeOfNegotiation |
P9608
|
FINISHED |
| Object | bilateral negotiation |
—
|
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: bilateral negotiation | Statement: [Reagan–Gorbachev summits, typeOfNegotiation, bilateral negotiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfNegotiation Context triple: [Reagan–Gorbachev summits, typeOfNegotiation, bilateral negotiation]
-
A.
negotiation
Indicates a process in which two or more parties communicate and make offers and counteroffers to reach a mutually acceptable agreement.
-
B.
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).
-
C.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
D.
negotiationRound
Indicates a specific stage or iteration within an ongoing negotiation process between parties.
-
E.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
- F. None of above. chosen
Provenance (4 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.