Triple
T8650116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Air (M2, 2022) |
E205076
|
entity |
| Predicate | powerAdapterOption |
P41267
|
FINISHED |
| Object | 30W USB-C power adapter |
—
|
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: 30W USB-C power adapter | Statement: [MacBook Air (M2, 2022), powerAdapterOption, 30W USB-C power adapter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerAdapterOption Context triple: [MacBook Air (M2, 2022), powerAdapterOption, 30W USB-C power adapter]
-
A.
powerAdapter
chosen
Indicates that one entity serves as a power adapter, converting or supplying electrical power for another entity.
-
B.
powerAdapterWattage
Indicates the electrical power capacity, in watts, that a power adapter can supply.
-
C.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
supportsPowerDelivery
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4813d0548190b203e594acc38c8f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.