Triple
T18734450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barakar River |
E458123
|
entity |
| Predicate | Tilaiya DamPurpose |
P22890
|
FINISHED |
| Object | hydroelectric power generation |
—
|
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: hydroelectric power generation | Statement: [Barakar River, Tilaiya DamPurpose, hydroelectric power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tilaiya DamPurpose Context triple: [Barakar River, Tilaiya DamPurpose, hydroelectric power generation]
-
A.
reservoirCreatedByDam
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
B.
isOneOfLargestDamsIn
Indicates that a dam ranks among the largest dams within a specified geographic region or jurisdiction.
-
C.
typeOfDamProject
Indicates that a given project is classified as a dam-related project (i.e., it is a project whose type is a dam project).
-
D.
numberOfDams
Indicates the quantity of dams associated with or present in a given entity or context.
-
E.
damPurpose
chosen
Indicates the primary function or intended use for which a dam has been constructed or is operated.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d7a06788190a8e09c657aaeb8e5 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.