Triple
T36663739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.0 |
E905201
|
entity |
| Predicate | powerDeliveryMaxCurrent |
P10589
|
FINISHED |
| Object | 500 mA |
—
|
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: 500 mA | Statement: [USB 1.0, powerDeliveryMaxCurrent, 500 mA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDeliveryMaxCurrent Context triple: [USB 1.0, powerDeliveryMaxCurrent, 500 mA]
-
A.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
B.
maxPowerDelivery
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
C.
supportsMaximumCurrent
chosen
Indicates that one entity is capable of handling or allowing a specified maximum electric current for another entity or connection.
-
D.
ACChargingPowerMax
Indicates the maximum electrical power that can be delivered to charge a device or system when using AC (alternating current).
-
E.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:12 p.m.