Triple
T4065795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAD750 |
E86319
|
entity |
| Predicate | typicalPowerConsumption |
P7394
|
FINISHED |
| Object | 5 W |
—
|
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: 5 W | Statement: [RAD750, typicalPowerConsumption, 5 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPowerConsumption Context triple: [RAD750, typicalPowerConsumption, 5 W]
-
A.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
-
B.
energyUse
chosen
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
C.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
-
D.
usesElectricityStandard
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
E.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf58d9c8190936e453b0d397cb0 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.