Triple
T33045720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decision 1/CP.13 |
E845591
|
entity |
| Predicate | followedByProcess |
P153180
|
FINISHED |
| Object | negotiations leading to the Copenhagen Accord |
—
|
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: negotiations leading to the Copenhagen Accord | Statement: [Decision 1/CP.13, followedByProcess, negotiations leading to the Copenhagen Accord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByProcess Context triple: [Decision 1/CP.13, followedByProcess, negotiations leading to the Copenhagen Accord]
-
A.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
B.
followedByInSequence
chosen
Indicates that one event or element directly succeeds another in an ordered sequence.
-
C.
followedByInProtocol
Indicates that one step, action, or event in a protocol occurs immediately after another as the next prescribed step.
-
D.
followedByInContext
Indicates that one element directly succeeds another within a specific contextual sequence or ordering.
-
E.
followedByInProductionOrder
Indicates that one process, step, or item directly succeeds another in a defined production sequence or workflow order.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:24 a.m.