Triple
T38495391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta V Dam |
E919676
|
entity |
| Predicate | plantCommissionedUnit3 |
P191435
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Teesta V Dam, plantCommissionedUnit3, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantCommissionedUnit3 Context triple: [Teesta V Dam, plantCommissionedUnit3, 2008]
-
A.
nuclearPowerStationUnit
Indicates a relationship where an individual unit (such as a reactor or generating block) is part of or belongs to a specific nuclear power station.
-
B.
generatingUnitCount
Indicates the number of generating units associated with or involved in a given entity or context.
-
C.
generationUnits
Indicates a relationship where specific units or components are responsible for generating or producing something within a system or process.
-
D.
plannedPowerplant
Indicates that a power plant is intended or scheduled to be built or developed, but is not yet constructed or operational.
-
E.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
- F. None of above. chosen
Provenance (4 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.