Triple
T32078170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Transmission Corporation Limited |
E819214
|
entity |
| Predicate | gridVoltageLevelsHandled |
P34711
|
FINISHED |
| Object | 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: 400 kV | Statement: [Tamil Nadu Transmission Corporation Limited, gridVoltageLevelsHandled, 400 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridVoltageLevelsHandled Context triple: [Tamil Nadu Transmission Corporation Limited, gridVoltageLevelsHandled, 400 kV]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
storesMultipleVoltageLevels
Indicates that an entity is capable of holding or maintaining more than one distinct voltage level simultaneously or over time.
-
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.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
E.
usesVoltageLevelsPerCell
Indicates that an entity operates or is configured using specific voltage levels defined on a per-cell basis.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b576472881908dcf86eaf238b4c7 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.