Triple
T33001177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kattappana |
E844367
|
entity |
| Predicate | nearestMajorHydelProjectRegion |
P45677
|
FINISHED |
| Object | Idukki hydel project area |
—
|
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: Idukki hydel project area | Statement: [Kattappana, nearestMajorHydelProjectRegion, Idukki hydel project area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorHydelProjectRegion Context triple: [Kattappana, nearestMajorHydelProjectRegion, Idukki hydel project area]
-
A.
nearestMajorRiverTown
Indicates that one town is the closest significant river-based settlement to another location or town.
-
B.
hasHydroelectricInfrastructureNearby
Indicates that there is hydroelectric infrastructure located in close proximity to the referenced entity.
-
C.
isHydroelectricProjectOn
Indicates that a hydroelectric project is located on or situated along a specified water body or site.
-
D.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
-
E.
nearbyMajorDam
chosen
Indicates that one entity is located close to a significant dam structure in its surrounding area.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:22 a.m.