Triple
T11234763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta Low Dam III |
E265913
|
entity |
| Predicate | gridConnectionVoltageLevel |
P34711
|
FINISHED |
| Object | 132 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: 132 kV | Statement: [Teesta Low Dam III, gridConnectionVoltageLevel, 132 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridConnectionVoltageLevel Context triple: [Teesta Low Dam III, gridConnectionVoltageLevel, 132 kV]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
gridInterconnection
Indicates a connection or linkage between electrical grids that allows power exchange or coordinated operation.
-
C.
gridConnectionAgreementWith
Indicates an agreement establishing the terms and conditions under which one party is connected to another party’s electrical grid.
-
D.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
E.
gridConnectionCountry
Indicates that an entity’s electrical grid is connected to, or integrated with, the power grid of a specified country.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.