Triple
T19780190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mokelumne River Fish Hatchery |
E475110
|
entity |
| Predicate | primarySpeciesRaised |
P38078
|
FINISHED |
| Object | Chinook salmon |
—
|
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: Chinook salmon | Statement: [Mokelumne River Fish Hatchery, primarySpeciesRaised, Chinook salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySpeciesRaised Context triple: [Mokelumne River Fish Hatchery, primarySpeciesRaised, Chinook salmon]
-
A.
primaryBreedingSpecies
Indicates that one species serves as the main or predominant breeding partner or host in relation to another species.
-
B.
primaryLivestock
Indicates that the specified livestock type is the main or most important kind of animal raised or kept by an entity.
-
C.
hasPrimaryFishSpecies
chosen
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
D.
mainPreySpecies
Indicates the species that serves as the primary prey or main food source for a given predator.
-
E.
firstOwnerSpecies
Indicates that the subject is the species of the entity that originally owned or possessed the object.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65382ff308190832800dd60675f7a |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.