Triple
T9546385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cattaraugus Creek |
E230298
|
entity |
| Predicate | hasSteelheadRun |
P89723
|
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: [Cattaraugus Creek, hasSteelheadRun, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSteelheadRun Context triple: [Cattaraugus Creek, hasSteelheadRun, yes]
-
A.
hasRiverActivity
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
-
B.
runOfTheRiver
Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large reservoir.
-
C.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
D.
hasFishPassage
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.
-
E.
recognizedAsStateFishSince
Indicates that an entity has been officially designated as the state fish of a particular jurisdiction starting from a specified date.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9902fca081909125660ae6336d3f |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:02 p.m.