Triple
T32358651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psetta maxima |
E826799
|
entity |
| Predicate | fisheries |
P174456
|
FINISHED |
| Object | target of trawl 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: target of trawl fisheries | Statement: [Psetta maxima, fisheries, target of trawl fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheries Context triple: [Psetta maxima, fisheries, target of trawl fisheries]
-
A.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
B.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
C.
supportsFishery
Indicates that one entity provides resources, conditions, or actions that maintain or enhance the viability of a fishery.
-
D.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
E.
gameFish
Indicates a relationship where an animal is considered a fish that is commonly pursued or valued in recreational or sport fishing.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:49 a.m.