Triple
T14905266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Sport Fish |
E360112
|
entity |
| Predicate | typeOfFisheriesManaged |
P33588
|
FINISHED |
| Object | sport fisheries |
—
|
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: sport fisheries | Statement: [Division of Sport Fish, typeOfFisheriesManaged, sport fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFisheriesManaged Context triple: [Division of Sport Fish, typeOfFisheriesManaged, sport fisheries]
-
A.
managedForFisheriesBy
Indicates that the management or oversight of fisheries-related activities or resources is carried out by a specified agent or authority.
-
B.
fisheryType
chosen
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
D.
typeOfProtectedAreasManaged
Indicates the specific categories or kinds of protected areas that an entity is responsible for managing.
-
E.
majorFisheryRegion
Indicates that a location is recognized as a primary or significant region for fishing activities or fishery production.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:12 a.m.