Triple
T4688257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha Amendment to the Kyoto Protocol |
E103971
|
entity |
| Predicate | commitmentPeriodStartDate |
P57230
|
FINISHED |
| Object | 2013-01-01 |
—
|
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: 2013-01-01 | Statement: [Doha Amendment to the Kyoto Protocol, commitmentPeriodStartDate, 2013-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commitmentPeriodStartDate Context triple: [Doha Amendment to the Kyoto Protocol, commitmentPeriodStartDate, 2013-01-01]
-
A.
grantPeriodStart
Indicates the date or time at which a grant’s active period or coverage begins.
-
B.
firstCommitmentPeriod
chosen
Indicates the initial time span or phase during which an agreed obligation, contract, or policy is first in effect.
-
C.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
D.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
E.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
- 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.