Triple
T29849514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spring Creek Recreation Area |
E758024
|
entity |
| Predicate | hasFishingTarget |
P45992
|
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: [Spring Creek Recreation Area, hasFishingTarget, walleye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingTarget Context triple: [Spring Creek Recreation Area, hasFishingTarget, walleye]
-
A.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
isFishingArea
Indicates that a location or region is designated or used as an area where fishing activities take place.
-
C.
hasFishingEventType
Indicates the specific type or category of a fishing-related event associated with an entity.
-
D.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
E.
hasFishingSeason
Indicates that there is a defined time period during which fishing for a particular resource or in a particular area is permitted or regulated.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 5:43 p.m.