Triple
T25425869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 7 |
E637113
|
entity |
| Predicate | supportsVoltageRegulation |
P34296
|
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: [Socket 7, supportsVoltageRegulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVoltageRegulation Context triple: [Socket 7, supportsVoltageRegulation, true]
-
A.
hasPowerRegulator
chosen
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
B.
hasTypeOfPowerRegulated
Indicates that one entity exercises a specific kind of power or authority that is subject to regulation or control by another entity or governing framework.
-
C.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
D.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
E.
voltageInput
Indicates that an entity serves as or provides an electrical voltage supplied to another entity or system.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 21, 2026, 1:57 p.m.