Triple
T11115411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-A |
E262872
|
entity |
| Predicate | maximumCurrent |
P10796
|
FINISHED |
| Object | 500 mA for USB 2.0 default |
—
|
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 for USB 2.0 default | Statement: [USB Type-A, maximumCurrent, 500 mA for USB 2.0 default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCurrent Context triple: [USB Type-A, maximumCurrent, 500 mA for USB 2.0 default]
-
A.
maxCurrent
chosen
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
B.
supportsMaximumCurrent
Indicates that one entity is capable of handling or allowing a specified maximum electric current for another entity or connection.
-
C.
maximumDischarge
Indicates the greatest allowable or observed rate at which something can be discharged or released from a source.
-
D.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
-
E.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa7254c8190abce35696ad2be03 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.