Triple
T299624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Power Delivery |
E6169
|
entity |
| Predicate | supportsMaximumCurrent |
P10589
|
FINISHED |
| Object | 5 A |
—
|
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 A | Statement: [USB Power Delivery, supportsMaximumCurrent, 5 A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMaximumCurrent Context triple: [USB Power Delivery, supportsMaximumCurrent, 5 A]
-
A.
hasMajorCurrent
Indicates that an entity currently has a primary field of study or specialization.
-
B.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
C.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
D.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
E.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.