Triple
T15696075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boundary Dam |
E380461
|
entity |
| Predicate | hasFishPassageMeasures |
P50471
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Boundary Dam, hasFishPassageMeasures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishPassageMeasures Context triple: [Boundary Dam, hasFishPassageMeasures, yes]
-
A.
hasFishPassage
chosen
Indicates that there exists a structure or feature that allows fish to move or migrate through, past, or around a barrier such as a dam or weir.
-
B.
hasFishPassageIssues
Indicates that there are problems or barriers affecting the ability of fish to move through a waterway or structure.
-
C.
fishwaysConstructedBy
Indicates that a fishway (a structure enabling fish passage) is built or installed by a specified agent or organization.
-
D.
hasLockAndDamSystem
Indicates that one entity possesses or is equipped with a system of locks and dams used to control water levels and facilitate navigation.
-
E.
blocksFishMigration
Indicates that one entity obstructs or prevents the movement or migratory passage of fish between habitats.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.