Triple
T21959165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harriman Dam |
E542275
|
entity |
| Predicate | isPartOfCascadeOn |
P73944
|
FINISHED |
| Object | Deerfield River |
—
|
NE NERFINISHED |
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: Deerfield River | Statement: [Harriman Dam, isPartOfCascadeOn, Deerfield River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCascadeOn Context triple: [Harriman Dam, isPartOfCascadeOn, Deerfield River]
-
A.
partOfCascade
chosen
Indicates that one event, process, or component functions as a step or segment within a larger sequential cascade.
-
B.
isCascading
Indicates that one event, action, or effect triggers a chain of subsequent related events, actions, or effects.
-
C.
cascadeType
Indicates how operations performed on one entity (such as create, update, or delete) are automatically propagated to its related entities.
-
D.
isMajorCascadeOf
Indicates that one event, process, or reaction is the primary or dominant cascade resulting from another, typically triggering a large-scale or critical chain of subsequent effects.
-
E.
belongsToCycle
Indicates that an entity is part of, or contained within, a specific cycle or cyclic structure.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244204f081909742d4fe138610d6 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.