Triple
T10294614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Region of Ecuador |
E241449
|
entity |
| Predicate | fisheriesProduct |
P92956
|
FINISHED |
| Object | shrimp |
—
|
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: shrimp | Statement: [Coastal Region of Ecuador, fisheriesProduct, shrimp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheriesProduct Context triple: [Coastal Region of Ecuador, fisheriesProduct, shrimp]
-
A.
aquacultureProduct
Indicates that something is a product derived from aquaculture activities, such as the farming or cultivation of aquatic organisms.
-
B.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
seafoodSpecialty
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
D.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
E.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d5e0f88190be3e23ba2511a1e9 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:42 a.m.