Triple
T32958471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renewables Obligation (historical) |
E843168
|
entity |
| Predicate | closureToNewAccreditationYear |
P175436
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Renewables Obligation (historical), closureToNewAccreditationYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureToNewAccreditationYear Context triple: [Renewables Obligation (historical), closureToNewAccreditationYear, 2017]
-
A.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
B.
usesAccreditationCycle
Indicates that one entity applies or follows a particular accreditation cycle associated with another entity.
-
C.
formerAccreditation
Indicates that an entity previously held a particular accreditation or certified status but no longer does.
-
D.
reaffirmationYear
Indicates the year in which a previously established agreement, decision, or commitment is formally confirmed or renewed.
-
E.
accessionPeriod
Indicates the time span during which an entity is formally acquired, admitted, or granted entry into a system, collection, or status.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:21 a.m.