Triple
T425291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Mini-B |
E8193
|
entity |
| Predicate | typicalCurrentLimit |
P10796
|
FINISHED |
| Object | up to 500 mA in USB 2.0 host ports |
—
|
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 500 mA in USB 2.0 host ports | Statement: [USB Mini-B, typicalCurrentLimit, up to 500 mA in USB 2.0 host ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCurrentLimit Context triple: [USB Mini-B, typicalCurrentLimit, up to 500 mA in USB 2.0 host ports]
-
A.
supportsMaximumCurrent
Indicates that one entity is capable of handling or allowing a specified maximum electric current for another entity or connection.
-
B.
maxCurrent
chosen
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
C.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.