Triple
T2796423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Display XDR |
E53046
|
entity |
| Predicate | powerDeliveryOverThunderbolt |
P4616
|
FINISHED |
| Object | 96 W |
—
|
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: 96 W | Statement: [Pro Display XDR, powerDeliveryOverThunderbolt, 96 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDeliveryOverThunderbolt Context triple: [Pro Display XDR, powerDeliveryOverThunderbolt, 96 W]
-
A.
supportsThunderbolt
Indicates that one entity provides compatibility with or the capability to use Thunderbolt technology for another entity.
-
B.
supportsPowerDelivery
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
-
C.
maxPowerDelivery
chosen
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
D.
thunderboltPortsCount
Indicates the number of Thunderbolt ports that an entity has.
-
E.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.