Triple
T5015635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning connector |
E112734
|
entity |
| Predicate | dataProtocolSupport |
P35980
|
FINISHED |
| Object | USB 2.0 |
—
|
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: USB 2.0 | Statement: [Lightning connector, dataProtocolSupport, USB 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProtocolSupport Context triple: [Lightning connector, dataProtocolSupport, USB 2.0]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
supportsMultipleDataAndDisplayProtocols
Indicates that an entity is capable of handling more than one type of data protocol and more than one type of display protocol.
-
C.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
D.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
E.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.