Triple
T18619527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 Accord |
E455111
|
entity |
| Predicate | includesCommitmentType |
P445
|
FINISHED |
| Object | political 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: political commitments | Statement: [COP15 Accord, includesCommitmentType, political commitments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommitmentType Context triple: [COP15 Accord, includesCommitmentType, political commitments]
-
A.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
-
B.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
C.
commitmentGrade
Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
-
D.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
E.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.