Triple
T29391029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QT Py boards |
E745368
|
entity |
| Predicate | supportsPowerVia |
P5993
|
FINISHED |
| Object | USB-C |
—
|
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 | Statement: [QT Py boards, supportsPowerVia, USB-C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPowerVia Context triple: [QT Py boards, supportsPowerVia, USB-C]
-
A.
supportedPower
Indicates that an entity is capable of providing, handling, or operating at a specified level or range of power.
-
B.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
-
C.
supportsPowerDelivery
chosen
Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
Created at: April 28, 2026, 2:42 p.m.