Triple
T299648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Power Delivery |
E6169
|
entity |
| Predicate | enablesAlternateModes |
P203
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [USB Power Delivery, enablesAlternateModes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesAlternateModes Context triple: [USB Power Delivery, enablesAlternateModes, true]
-
A.
definesPoweringMode
Indicates that one entity specifies or determines the operating or powering mode used by another entity.
-
B.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
C.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.