Triple
T4524825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoto Protocol |
E103350
|
entity |
| Predicate | setsBaselinePeriod |
P57233
|
FINISHED |
| Object | 1990 for most Annex I Parties |
—
|
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: 1990 for most Annex I Parties | Statement: [Kyoto Protocol, setsBaselinePeriod, 1990 for most Annex I Parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsBaselinePeriod Context triple: [Kyoto Protocol, setsBaselinePeriod, 1990 for most Annex I Parties]
-
A.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
B.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
-
C.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
- F. None of above. chosen
Provenance (4 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5773341c8190bf27745feb863575 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.