Triple
T13523565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Ronkonkoma |
E322961
|
entity |
| Predicate | hasRecreationalFish |
P45992
|
FINISHED |
| Object | largemouth bass |
—
|
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: largemouth bass | Statement: [Lake Ronkonkoma, hasRecreationalFish, largemouth bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalFish Context triple: [Lake Ronkonkoma, hasRecreationalFish, largemouth bass]
-
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.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
C.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
D.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
-
E.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa535cc81908d0018fef81a2848 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.