Triple
T25425752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P6 |
E637110
|
entity |
| Predicate | notableImprovementOverPredecessor |
P48818
|
FINISHED |
| Object | higher instructions per cycle |
—
|
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: higher instructions per cycle | Statement: [P6, notableImprovementOverPredecessor, higher instructions per cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableImprovementOverPredecessor Context triple: [P6, notableImprovementOverPredecessor, higher instructions per cycle]
-
A.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
-
C.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
D.
distinctionFromPredecessors
Indicates that an entity is characterized by features or qualities that differentiate it from its predecessors.
-
E.
notableAdvance
chosen
Indicates that one entity represents a significant improvement, breakthrough, or progress over another in a particular domain or context.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 21, 2026, 1:57 p.m.