Triple
T19676770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathpa Jhakri Dam |
E472471
|
entity |
| Predicate | operatorAbbreviation |
P43
|
FINISHED |
| Object | SJVN |
—
|
NE NERFINISHED |
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: SJVN | Statement: [Nathpa Jhakri Dam, operatorAbbreviation, SJVN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SJVN Context triple: [Nathpa Jhakri Dam, operatorAbbreviation, SJVN]
-
A.
SJVN
SJVN is an Indian public sector company primarily engaged in the generation and sale of hydroelectric power, along with diversification into other energy sources.
-
B.
SJVN Limited
chosen
SJVN Limited is an Indian public sector company primarily engaged in the generation and development of hydroelectric power and other energy projects.
-
C.
SVJ
SVJ is the three-letter IATA airport code for Svolvær Airport, Helle in Norway.
-
D.
EVN
EVN is a major news exchange service operated under the Eurovision framework, facilitating the sharing of news footage and content among broadcasters.
-
E.
EVN
EVN is the three-letter IATA airport code for Zvartnots International Airport serving Yerevan, Armenia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bbea8c8190b0ad841d95068e0e |
completed | April 20, 2026, 3:09 p.m. |
Created at: April 10, 2026, 1:45 p.m.