Triple
T11444404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harsud |
E271226
|
entity |
| Predicate | projectTypeCausingSubmergence |
P61258
|
FINISHED |
| Object | hydroelectric dam |
—
|
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 dam | Statement: [Harsud, projectTypeCausingSubmergence, hydroelectric dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectTypeCausingSubmergence Context triple: [Harsud, projectTypeCausingSubmergence, hydroelectric dam]
-
A.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
B.
typeOfDamProject
chosen
Indicates that a given project is classified as a dam-related project (i.e., it is a project whose type is a dam project).
-
C.
formedBySubmerging
Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
-
D.
typeOfDam
Indicates the specific kind or classification of a dam associated with an entity.
-
E.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088a66f48190b2b4a56cd62097cf |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.