Triple
T38455714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.1 |
E912309
|
entity |
| Predicate | connectorCompatibility |
P1374
|
FINISHED |
| Object | USB Type-A |
—
|
NE NERFINISHED |
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: USB Type-A | Statement: [USB 1.1, connectorCompatibility, USB Type-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectorCompatibility Context triple: [USB 1.1, connectorCompatibility, USB Type-A]
-
A.
automationCompatibility
Indicates that one entity can be reliably and effectively operated, controlled, or integrated through automated systems or processes in relation to another entity.
-
B.
compatibleViaAdapterWith
Indicates that two entities, which are not directly compatible, can function together when connected through a specific adapter.
-
C.
busCompatibility
Indicates that two hardware or software components can operate together correctly over the same communication bus or interface.
-
D.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
E.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:31 p.m.