Triple
T25425870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 7 |
E637113
|
entity |
| Predicate | supportsSplitVoltage |
P175607
|
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, supportsSplitVoltage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSplitVoltage Context triple: [Socket 7, supportsSplitVoltage, true]
-
A.
storesMultipleVoltageLevels
Indicates that an entity is capable of holding or maintaining more than one distinct voltage level simultaneously or over time.
-
B.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
C.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
D.
typicalVoltageSpacing
Indicates the usual or standard voltage difference that is maintained or expected between two related electrical points or levels.
-
E.
usesVoltageLevelsPerCell
Indicates that an entity operates or is configured using specific voltage levels defined on a per-cell basis.
- F. None of above. chosen
Provenance (4 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 21, 2026, 1:57 p.m.