Triple
T20549680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMP6 |
E504563
|
entity |
| Predicate | typeOfAgreementDiscussed |
P38198
|
FINISHED |
| Object | legally binding emission reduction commitments |
—
|
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: legally binding emission reduction commitments | Statement: [CMP6, typeOfAgreementDiscussed, legally binding emission reduction commitments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAgreementDiscussed Context triple: [CMP6, typeOfAgreementDiscussed, legally binding emission reduction commitments]
-
A.
hasTypeOfAgreement
chosen
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
B.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
-
C.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
D.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
E.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d739bc8190b2bf60f82d2ade0c |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.