Triple
T4656960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntersville Lake |
E102431
|
entity |
| Predicate | primaryFishSpecies |
P38078
|
FINISHED |
| Object | largemouth bass |
—
|
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: largemouth bass | Statement: [Guntersville Lake, primaryFishSpecies, largemouth bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFishSpecies Context triple: [Guntersville Lake, primaryFishSpecies, largemouth bass]
-
A.
hasPrimaryFishSpecies
chosen
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
B.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
C.
primaryMarineSpeciesObserved
Indicates that the specified marine species is the main or most frequently observed species in a given observation or survey context.
-
D.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
E.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd631a855c81909773737fd238a14d |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.