Triple
T10922157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topaz Lake (Nevada portion) |
E257973
|
entity |
| Predicate | peakFishingSeason |
P78242
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Topaz Lake (Nevada portion), peakFishingSeason, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakFishingSeason Context triple: [Topaz Lake (Nevada portion), peakFishingSeason, spring]
-
A.
hasFishingSeason
chosen
Indicates that there is a defined time period during which fishing for a particular resource or in a particular area is permitted or regulated.
-
B.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
C.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
D.
fishingPopularity
Indicates how common or favored fishing is among a group of people or within a particular area or time period.
-
E.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708d1fb88190bb33b72d4330ce11 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.