Triple
T31640993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Estes |
E807454
|
entity |
| Predicate | recreationalFishingSpecies |
P45992
|
FINISHED |
| Object | rainbow trout |
—
|
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: rainbow trout | Statement: [Lake Estes, recreationalFishingSpecies, rainbow trout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalFishingSpecies Context triple: [Lake Estes, recreationalFishingSpecies, rainbow trout]
-
A.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
B.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
D.
typicalFishType
Indicates that one entity is the fish type that is most commonly or characteristically associated with the other entity.
-
E.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:49 p.m.