Triple
T16934054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trisopterus minutus |
E410784
|
entity |
| Predicate | fisheryUse |
P92956
|
FINISHED |
| Object | used for fish meal |
—
|
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: used for fish meal | Statement: [Trisopterus minutus, fisheryUse, used for fish meal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheryUse Context triple: [Trisopterus minutus, fisheryUse, used for fish meal]
-
A.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
B.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
C.
fisheriesProduct
chosen
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
D.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
E.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.