Triple
T3137827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shivanasamudra Hydroelectric Station |
E65575
|
entity |
| Predicate | hasTurbineType |
P11311
|
FINISHED |
| Object | hydraulic turbine |
—
|
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: hydraulic turbine | Statement: [Shivanasamudra Hydroelectric Station, hasTurbineType, hydraulic turbine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurbineType Context triple: [Shivanasamudra Hydroelectric Station, hasTurbineType, hydraulic turbine]
-
A.
turbineType
chosen
Indicates the specific kind or category of turbine associated with or used by an entity.
-
B.
hasTurbines
Indicates that one entity is equipped with, contains, or includes one or more turbines in relation to another entity.
-
C.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
D.
hasBladeCountPerTurbine
Indicates the number of blades associated with each individual turbine.
-
E.
turbineCapacity
Indicates the power-generating capacity or rated output of a turbine.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada574509c81908a88bb10ea35516d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.