Triple
T7771356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Moy |
E179075
|
entity |
| Predicate | hasFishingSeason |
P78242
|
FINISHED |
| Object | salmon season |
—
|
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: salmon season | Statement: [River Moy, hasFishingSeason, salmon season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingSeason Context triple: [River Moy, hasFishingSeason, salmon season]
-
A.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
hasDivingSeason
Indicates that there is a specific time period during which diving activities are permitted, optimal, or typically occur for a given entity or location.
-
C.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
-
D.
hasSeasonalSpecies
Indicates that certain species are present or occur only during specific seasons in relation to a given context or location.
-
E.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c7045ebae88190a04c8f972795e615 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702a78edc819090c3448d33c8c381 |
completed | March 27, 2026, 10:20 p.m. |
Created at: March 27, 2026, 4:11 p.m.