Triple
T19822092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMP14 |
E476219
|
entity |
| Predicate | convenedTo |
P39907
|
FINISHED |
| Object | negotiate implementation 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: negotiate implementation of the Kyoto Protocol | Statement: [CMP14, convenedTo, negotiate implementation of the Kyoto Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedTo Context triple: [CMP14, convenedTo, negotiate implementation of the Kyoto Protocol]
-
A.
convenedFor
chosen
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
B.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
C.
convenedAfter
Indicates that one event, meeting, or gathering was formally brought together at a time later than another specified event.
-
D.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
E.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654ffb37c8190be540a793befe16c |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.