Triple
T4753964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karcham Wangtoo Dam |
E105541
|
entity |
| Predicate | isMajorProjectIn |
P12153
|
FINISHED |
| Object | Himachal Pradesh power sector |
—
|
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: Himachal Pradesh power sector | Statement: [Karcham Wangtoo Dam, isMajorProjectIn, Himachal Pradesh power sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorProjectIn Context triple: [Karcham Wangtoo Dam, isMajorProjectIn, Himachal Pradesh power sector]
-
A.
majorProject
chosen
Indicates that an entity is a primary, large-scale, or most significant project associated with another entity.
-
B.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
D.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
E.
isMajorLineOf
Indicates that one entity is a primary or principal route, branch, or component within the structure or network represented by the other entity.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e72d1c81908eb60960751e52b1 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.