Triple
T25933238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt 4 |
E653483
|
entity |
| Predicate | supportsExternalGPUs |
P105951
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Thunderbolt 4, supportsExternalGPUs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExternalGPUs Context triple: [Thunderbolt 4, supportsExternalGPUs, yes]
-
A.
supportsExternalGPU
chosen
Indicates that an entity is capable of working with or providing connectivity for an external graphics processing unit (eGPU).
-
B.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
C.
supportsGPUBrand
Indicates that one entity is compatible with, or provides functional support for, a specified GPU brand.
-
D.
suppliedGPUFor
Indicates that one entity provided or furnished a GPU to another entity for its use or operation.
-
E.
hasGPUDetails
Indicates that an entity is associated with specific details or specifications about a GPU (graphics processing unit).
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 22, 2026, 8:37 a.m.