Triple
T32446296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walleye Capital of the World |
E829155
|
entity |
| Predicate | associatedWithFishSpecies |
P38078
|
FINISHED |
| Object | walleye |
—
|
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: walleye | Statement: [Walleye Capital of the World, associatedWithFishSpecies, walleye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFishSpecies Context triple: [Walleye Capital of the World, associatedWithFishSpecies, walleye]
-
A.
speciesAssociatedWith
Indicates that there is a relevant connection or linkage between a species and another entity (such as a habitat, condition, or feature), without specifying the exact nature of that relationship.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
nativeFish
Indicates that the fish species is originally from, and naturally occurs in, the specified geographic area or ecosystem.
-
D.
hasPrimaryFishSpecies
chosen
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
E.
hasNearbyFishSpecies
Indicates that one entity has fish species occurring in close spatial proximity to 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:56 a.m.