Triple
T11100679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusoe |
E262493
|
entity |
| Predicate | powerManagementTechnique |
P11923
|
FINISHED |
| Object | dynamic frequency scaling |
—
|
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: dynamic frequency scaling | Statement: [Crusoe, powerManagementTechnique, dynamic frequency scaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerManagementTechnique Context triple: [Crusoe, powerManagementTechnique, dynamic frequency scaling]
-
A.
powerOptimizationFor
Indicates a relationship where one entity is used to improve, manage, or optimize the power consumption or power efficiency of another entity.
-
B.
powerOptimized
Indicates that an entity operates or is configured in a way that minimizes energy consumption or maximizes power efficiency.
-
C.
powerOption
Indicates that one entity provides or specifies a particular power-related configuration or choice available to another entity.
-
D.
maintainsPowerThrough
Indicates that one entity preserves or secures its authority, control, or dominance by means of another entity or specified mechanism.
-
E.
hasEnergyManagement
chosen
Indicates that an entity possesses or is associated with a system, capability, or function for monitoring, controlling, or optimizing energy use.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a29ee6c819092bc0da3f9255389 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.