Triple
T36049830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brilliant Substation |
E1042775
|
entity |
| Predicate | hasVoltageLevel |
P34711
|
FINISHED |
| Object | high-voltage transmission level |
—
|
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: high-voltage transmission level | Statement: [Brilliant Substation, hasVoltageLevel, high-voltage transmission level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoltageLevel Context triple: [Brilliant Substation, hasVoltageLevel, high-voltage transmission level]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
usesVoltageLevelsPerCell
Indicates that an entity operates or is configured using specific voltage levels defined on a per-cell basis.
-
C.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
storesMultipleVoltageLevels
Indicates that an entity is capable of holding or maintaining more than one distinct voltage level simultaneously or over time.
-
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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:07 p.m.