Triple
T32212215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle electrical power system |
E822837
|
entity |
| Predicate | nominalVoltageLevel |
P1870
|
FINISHED |
| Object | 28 V DC |
—
|
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: 28 V DC | Statement: [Space Shuttle electrical power system, nominalVoltageLevel, 28 V DC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominalVoltageLevel Context triple: [Space Shuttle electrical power system, nominalVoltageLevel, 28 V DC]
-
A.
gridVoltageLevel
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
symbolForVoltage
Indicates that one entity is the symbolic representation used to denote the voltage associated with another entity.
-
C.
usesVoltageLevelsPerCell
Indicates that an entity operates or is configured using specific voltage levels defined on a per-cell basis.
-
D.
usesElectricityVoltage
chosen
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
E.
typicalVoltagePerCell
Indicates the standard or commonly expected voltage value associated with each individual cell in a multi-cell system or device.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:37 a.m.