Triple
T36663791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 3.0 |
E905202
|
entity |
| Predicate | maximumBusPowerPerPort |
P97014
|
FINISHED |
| Object | 900 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: 900 mA | Statement: [USB 3.0, maximumBusPowerPerPort, 900 mA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBusPowerPerPort Context triple: [USB 3.0, maximumBusPowerPerPort, 900 mA]
-
A.
maxBusPowerPerPort
chosen
Indicates the maximum amount of power that can be supplied via the bus on a single port.
-
B.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
-
C.
maximumDevicesPerBus
Indicates the maximum number of devices that are allowed to be connected to a single bus.
-
D.
maxDevicesPerBus
Indicates the maximum number of devices that are allowed to be connected to a single bus.
-
E.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
- 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_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:12 p.m.