Triple
T9255061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clupea |
E222418
|
entity |
| Predicate | fisheriesManagementConcern |
P51236
|
FINISHED |
| Object | overfishing risk |
—
|
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: overfishing risk | Statement: [Clupea, fisheriesManagementConcern, overfishing risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheriesManagementConcern Context triple: [Clupea, fisheriesManagementConcern, overfishing risk]
-
A.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
B.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
fishingPolicy
chosen
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
D.
fishingImportance
Indicates the degree to which fishing plays a significant or prioritized role in relation to a given entity or context.
-
E.
hasMarineManagement
Indicates that an entity exercises authority or responsibility over the planning, regulation, or stewardship of marine areas or resources.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b3c314819096632b8263288aae |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.