Triple
T16385853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Day Dam |
E397919
|
entity |
| Predicate | fishPassageFacility |
P50471
|
FINISHED |
| Object | fish ladders |
—
|
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: fish ladders | Statement: [John Day Dam, fishPassageFacility, fish ladders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishPassageFacility Context triple: [John Day Dam, fishPassageFacility, fish ladders]
-
A.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
B.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
-
C.
nearbyFishery
Indicates that a fishery is located close to or within a short distance of a specified reference point or area.
-
D.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
E.
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.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263d260081909db9ac6016d5738a |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.