Triple
T13319883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IGBT |
E317285
|
entity |
| Predicate | hasSwitchingMode |
P12713
|
FINISHED |
| Object | hard switching |
—
|
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: hard switching | Statement: [IGBT, hasSwitchingMode, hard switching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSwitchingMode Context triple: [IGBT, hasSwitchingMode, hard switching]
-
A.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
B.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
C.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
D.
hasCoopMode
Indicates that something supports or includes a cooperative mode of operation or gameplay involving multiple participants working together.
-
E.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.