Triple
T31706193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universe of Energy |
E809186
|
entity |
| Predicate | refurbishedShowPremiereYear |
P116506
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Universe of Energy, refurbishedShowPremiereYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishedShowPremiereYear Context triple: [Universe of Energy, refurbishedShowPremiereYear, 1996]
-
A.
rebootPremiereDate
Indicates the date on which a rebooted version of a work (such as a series or franchise) is first released or premieres.
-
B.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
-
C.
revisedVersionPremiereYear
chosen
Indicates the year in which a revised version of a work was first premiered or publicly presented.
-
D.
refurbishedAs
Indicates that an entity has been renovated, restored, or upgraded and subsequently used or designated in a new or improved form or function.
-
E.
remasteredAt
Indicates that an existing work has been reprocessed or updated at a specific time or in a specific release to improve its quality or presentation.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:14 p.m.