Triple
T2971706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice President’s National Energy Policy Development Group |
E80294
|
entity |
| Predicate | publicationDateOfMainReport |
P30105
|
FINISHED |
| Object | May 2001 |
—
|
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: May 2001 | Statement: [Vice President’s National Energy Policy Development Group, publicationDateOfMainReport, May 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationDateOfMainReport Context triple: [Vice President’s National Energy Policy Development Group, publicationDateOfMainReport, May 2001]
-
A.
finalReportPublicationDate
Indicates the date on which the final report is officially published or made publicly available.
-
B.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
C.
publicationMonth
Indicates the calendar month in which a publication was released or made publicly available.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
hasPublicationDate
chosen
Indicates that an entity is associated with the specific date on which it was published.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9973ed6881908f11f49ca2e171df |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.