Triple
T7416454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walleye |
E171141
|
entity |
| Predicate | fishingPopularity |
P76826
|
FINISHED |
| Object | highly sought by anglers |
—
|
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: highly sought by anglers | Statement: [Walleye, fishingPopularity, highly sought by anglers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingPopularity Context triple: [Walleye, fishingPopularity, highly sought by anglers]
-
A.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
B.
fishingImportance
Indicates the degree to which fishing plays a significant or prioritized role in relation to a given entity or context.
-
C.
fishingPolicy
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
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. chosen
Provenance (4 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c7ae0c8190a8348d6223aeeecc |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.