Triple
T13685054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canistear Reservoir |
E328099
|
entity |
| Predicate | fishingRequires |
P51236
|
FINISHED |
| Object | New Jersey fishing license |
—
|
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: New Jersey fishing license | Statement: [Canistear Reservoir, fishingRequires, New Jersey fishing license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingRequires Context triple: [Canistear Reservoir, fishingRequires, New Jersey fishing license]
-
A.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
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.
fishingPolicy
chosen
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
E.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66f8acc8190b2a82b722930b995 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.