Triple
T30913766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Renewable Energy Agency |
E787524
|
entity |
| Predicate | statuteAdoptedOn |
P37784
|
FINISHED |
| Object | 2009-01-26 |
—
|
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: 2009-01-26 | Statement: [International Renewable Energy Agency, statuteAdoptedOn, 2009-01-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statuteAdoptedOn Context triple: [International Renewable Energy Agency, statuteAdoptedOn, 2009-01-26]
-
A.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
B.
dateOfFirstStatuteApproval
chosen
Indicates the date on which a statute (or legal act) was first formally approved.
-
C.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
D.
dateAdopted
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
E.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 8:51 p.m.