Triple
T299666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Power Delivery |
E6169
|
entity |
| Predicate | requiresCableType |
P1373
|
FINISHED |
| Object | electronically marked cable for 5 A operation |
—
|
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: electronically marked cable for 5 A operation | Statement: [USB Power Delivery, requiresCableType, electronically marked cable for 5 A operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCableType Context triple: [USB Power Delivery, requiresCableType, electronically marked cable for 5 A operation]
-
A.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
hasSternType
Indicates that an entity (typically a vessel) possesses a specific type or design of stern.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.