Triple
T5033763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilcomayo River |
E113369
|
entity |
| Predicate | hasFisheryType |
P33588
|
FINISHED |
| Object | artisanal fishery |
—
|
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: artisanal fishery | Statement: [Pilcomayo River, hasFisheryType, artisanal fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFisheryType Context triple: [Pilcomayo River, hasFisheryType, artisanal fishery]
-
A.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
B.
fisheryType
chosen
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
D.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
E.
isFishingPort
Indicates that a location functions primarily as a port where fishing vessels operate and fish-related activities such as landing, processing, or trading catch take place.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b68d8c8190b8e04fb406abdb0f |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.