Triple
T33101179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Olympia |
E847049
|
entity |
| Predicate | typicalFish |
P152950
|
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: [Lake Olympia, typicalFish, largemouth bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFish Context triple: [Lake Olympia, typicalFish, largemouth bass]
-
A.
typicalFishType
chosen
Indicates that one entity is the fish type that is most commonly or characteristically associated with the other entity.
-
B.
nativeFish
Indicates that the fish species is originally from, and naturally occurs in, the specified geographic area or ecosystem.
-
C.
gameFish
Indicates a relationship where an animal is considered a fish that is commonly pursued or valued in recreational or sport fishing.
-
D.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
E.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.