Triple
T25717407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Réseau de Transport d’Électricité |
E644897
|
entity |
| Predicate | gridVoltageRange |
P118761
|
FINISHED |
| Object | 63 kV to 400 kV |
—
|
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: 63 kV to 400 kV | Statement: [Réseau de Transport d’Électricité, gridVoltageRange, 63 kV to 400 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridVoltageRange Context triple: [Réseau de Transport d’Électricité, gridVoltageRange, 63 kV to 400 kV]
-
A.
typicalVoltageRange
chosen
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
B.
gridVoltageLevel
Indicates the electrical voltage level at which a power grid or network segment operates.
-
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.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
E.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6365288190ac46e37a887aa1e1 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:46 p.m.