Triple
T4524823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoto Protocol |
E103350
|
entity |
| Predicate | requiresReporting |
P31458
|
FINISHED |
| Object | national greenhouse gas inventories |
—
|
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: national greenhouse gas inventories | Statement: [Kyoto Protocol, requiresReporting, national greenhouse gas inventories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresReporting Context triple: [Kyoto Protocol, requiresReporting, national greenhouse gas inventories]
-
A.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
-
B.
requiresReportFrom
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
C.
requiredReportOn
chosen
Indicates that one entity is obligated to produce or submit a report concerning another entity or subject.
-
D.
canReport
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
-
E.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
- 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_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. |
Created at: March 20, 2026, 1:03 p.m.