Triple
T3618926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonneville Dam |
E76672
|
entity |
| Predicate | hasFishCountingFacility |
P50472
|
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: [Bonneville Dam, hasFishCountingFacility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishCountingFacility Context triple: [Bonneville Dam, hasFishCountingFacility, yes]
-
A.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
C.
hasJellyfishPopulation
Indicates that an entity possesses, contains, or supports a population of jellyfish.
-
D.
isFishingPort
Indicates that a location functions primarily as a port where fishing vessels operate and fish-related activities such as landing, processing, or trading catch take place.
-
E.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b72b3481909f4a09000d1815d9 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.