Triple
T38692504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torch Lake (Houghton County, Michigan) |
E949306
|
entity |
| Predicate | fishConsumptionAdvisory |
P191538
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Torch Lake (Houghton County, Michigan), fishConsumptionAdvisory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishConsumptionAdvisory Context triple: [Torch Lake (Houghton County, Michigan), fishConsumptionAdvisory, yes]
-
A.
fisheryReputation
Indicates the perceived quality, reliability, or standing of a fishery based on its practices, performance, and stakeholder opinions.
-
B.
Seafood Watch
Indicates a relationship in which an entity evaluates and advises on the environmental sustainability of seafood choices or fisheries.
-
C.
nearbyFishery
Indicates that a fishery is located close to or within a short distance of a specified reference point or area.
-
D.
containsFish
Indicates that one entity holds, includes, or has fish within its boundaries or contents.
-
E.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.