Triple
T4524801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoto Protocol |
E103350
|
entity |
| Predicate | firstCommitmentPeriod |
P57230
|
FINISHED |
| Object | 2008-2012 |
—
|
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: 2008-2012 | Statement: [Kyoto Protocol, firstCommitmentPeriod, 2008-2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommitmentPeriod Context triple: [Kyoto Protocol, firstCommitmentPeriod, 2008-2012]
-
A.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
-
B.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
C.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
D.
hasInaugurationPeriod
Indicates the time span during which an inauguration event takes place or is officially in effect.
-
E.
firstTermStart
Indicates that an entity marks the starting point or initial term in an ordered sequence, period, or agreement.
- 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.