Triple
T11305834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVI |
E267709
|
entity |
| Predicate | hotPlugSupport |
P10793
|
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: [DVI, hotPlugSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotPlugSupport Context triple: [DVI, hotPlugSupport, yes]
-
A.
isHotPluggable
chosen
Indicates that a device or component can be connected to or disconnected from a system while it is powered on and operating, without requiring a shutdown or restart.
-
B.
hotSwappable
Indicates that one component can be removed and replaced with another while the overall system remains powered on and operational.
-
C.
supportsPlugAndPlayLikeConfiguration
Indicates that one entity enables another to be configured in a plug-and-play–like manner, requiring minimal manual setup or integration effort.
-
D.
powerChange
Indicates a change in the level, amount, or state of power associated with an entity over time.
-
E.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.