Triple
T19996571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Rawson |
E494208
|
entity |
| Predicate | hasMainSpeciesFished |
P38078
|
FINISHED |
| Object | Argentine red 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: Argentine red shrimp | Statement: [Puerto Rawson, hasMainSpeciesFished, Argentine red shrimp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSpeciesFished Context triple: [Puerto Rawson, hasMainSpeciesFished, Argentine red shrimp]
-
A.
hasPrimaryFishSpecies
chosen
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
D.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
E.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe549108190947a4d1a587c08f8 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.