Triple
T3667395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Joseph Dam |
E77792
|
entity |
| Predicate | blocksFishMigration |
P50033
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chief Joseph Dam, blocksFishMigration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blocksFishMigration Context triple: [Chief Joseph Dam, blocksFishMigration, true]
-
A.
hasLockAndDamSystem
Indicates that one entity possesses or is equipped with a system of locks and dams used to control water levels and facilitate navigation.
-
B.
impactedRiver
Indicates that one entity has caused a significant effect, alteration, or disturbance to a river or its conditions.
-
C.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
D.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
E.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
- F. None of above. chosen
Provenance (4 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc402f5dc8190bd8d56a3c06e88f3 |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:25 p.m.