Triple
T4688258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha Amendment to the Kyoto Protocol |
E103971
|
entity |
| Predicate | commitmentPeriodEndDate |
P34836
|
FINISHED |
| Object | 2020-12-31 |
—
|
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: 2020-12-31 | Statement: [Doha Amendment to the Kyoto Protocol, commitmentPeriodEndDate, 2020-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commitmentPeriodEndDate Context triple: [Doha Amendment to the Kyoto Protocol, commitmentPeriodEndDate, 2020-12-31]
-
A.
grantPeriodEnd
Indicates the date or point in time when a grant’s active period or eligibility officially ends.
-
B.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
C.
associatedPeriodEnd
chosen
Indicates the ending point or final date of the time period with which something is associated.
-
D.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.