Triple
T8414949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blizzard |
E198709
|
entity |
| Predicate | comparedToPredecessor |
P82043
|
FINISHED |
| Object | offers higher performance per watt |
—
|
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: offers higher performance per watt | Statement: [Blizzard, comparedToPredecessor, offers higher performance per watt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparedToPredecessor Context triple: [Blizzard, comparedToPredecessor, offers higher performance per watt]
-
A.
emissionsComparedToPredecessor
Indicates how the emissions of an entity compare in magnitude (e.g., higher, lower, or equal) to those of its immediate predecessor.
-
B.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
E.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e443a08190983d9a0a61e0f781 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.