Triple
T767773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt |
E16212
|
entity |
| Predicate | powerDeliveryCapability |
P4616
|
FINISHED |
| Object | up to 10 watts in early versions |
—
|
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: up to 10 watts in early versions | Statement: [Thunderbolt, powerDeliveryCapability, up to 10 watts in early versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDeliveryCapability Context triple: [Thunderbolt, powerDeliveryCapability, up to 10 watts in early versions]
-
A.
supportsPowerDelivery
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
-
B.
maxPowerDelivery
chosen
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
C.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
D.
fastChargingCapability
Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
-
E.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.