Triple
T36663881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Micro-A |
E905204
|
entity |
| Predicate | roleInUSBOTG |
P203594
|
FINISHED |
| Object | A-device connector |
—
|
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: A-device connector | Statement: [USB Micro-A, roleInUSBOTG, A-device connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUSBOTG Context triple: [USB Micro-A, roleInUSBOTG, A-device connector]
-
A.
roleInOTG
chosen
Indicates that an entity holds a specific role or function within an organizational, operational, or task-oriented group (OTG).
-
B.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
C.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
D.
usbFeatures
Indicates that there exists a relationship specifying the USB-related capabilities or characteristics supported by an entity.
-
E.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: May 3, 2026, 4:12 p.m.