Triple
T11115351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 2.0 |
E262871
|
entity |
| Predicate | powerVoltage |
P1870
|
FINISHED |
| Object | 5 V |
—
|
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 V | Statement: [USB 2.0, powerVoltage, 5 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerVoltage Context triple: [USB 2.0, powerVoltage, 5 V]
-
A.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
B.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
C.
usesElectricityVoltage
chosen
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
approximateVoltage
Indicates that one entity represents or provides a value that is close to, but not necessarily exactly equal to, the voltage of another entity.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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.