Triple
T6704625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holyoke Dam |
E152968
|
entity |
| Predicate | fishPassageFor |
P50471
|
FINISHED |
| Object | American shad |
—
|
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: American shad | Statement: [Holyoke Dam, fishPassageFor, American shad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishPassageFor Context triple: [Holyoke Dam, fishPassageFor, American shad]
-
A.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
B.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
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.
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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.