Triple
T32357665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleuronectes platessa |
E826777
|
entity |
| Predicate | fisheryGear |
P81811
|
FINISHED |
| Object | bottom trawls |
—
|
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: bottom trawls | Statement: [Pleuronectes platessa, fisheryGear, bottom trawls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheryGear Context triple: [Pleuronectes platessa, fisheryGear, bottom trawls]
-
A.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
B.
fishingType
chosen
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
D.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
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.
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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9029508190b3e33e5dd44cf489 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:49 a.m.