Triple
T18807004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP18 |
E459899
|
entity |
| Predicate | adoptedDecisionOn |
P132425
|
FINISHED |
| Object | second commitment period of the Kyoto Protocol |
—
|
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: second commitment period of the Kyoto Protocol | Statement: [COP18, adoptedDecisionOn, second commitment period of the Kyoto Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedDecisionOn Context triple: [COP18, adoptedDecisionOn, second commitment period of the Kyoto Protocol]
-
A.
decisionAdoptedAt
chosen
Indicates that a decision was formally adopted or approved at a specific time or event.
-
B.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.