Triple
T767764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt |
E16212
|
entity |
| Predicate | usedConnectorInVersion4 |
P11239
|
FINISHED |
| Object | USB-C 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: USB-C connector | Statement: [Thunderbolt, usedConnectorInVersion4, USB-C connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedConnectorInVersion4 Context triple: [Thunderbolt, usedConnectorInVersion4, USB-C connector]
-
A.
usedInVersionRange
chosen
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
B.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
C.
alsoUsedBy
Indicates that something is additionally utilized or employed by another entity, beyond any primary or previously mentioned user.
-
D.
usesTConnectorsAtStations
Indicates that the subject employs T-shaped connectors at stations as part of its configuration or infrastructure.
-
E.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.