Triple
T6596297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishanganga Hydroelectric Plant |
E148483
|
entity |
| Predicate | headRaceTunnelLength |
P12895
|
FINISHED |
| Object | approximately 23.5 km |
—
|
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: approximately 23.5 km | Statement: [Kishanganga Hydroelectric Plant, headRaceTunnelLength, approximately 23.5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headRaceTunnelLength Context triple: [Kishanganga Hydroelectric Plant, headRaceTunnelLength, approximately 23.5 km]
-
A.
hasHeadraceTunnel
Indicates that an entity is connected to or equipped with a headrace tunnel that conveys water to a hydraulic structure or power-generating facility.
-
B.
hasTunnelLengthApprox
chosen
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
C.
tunnelCircumference
Indicates the circular distance around the inner boundary of a tunnel’s cross-section.
-
D.
coneLength
Indicates the length measurement of a cone-shaped structure associated with an entity.
-
E.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.