Triple
T13357298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodiak, Alaska |
E318725
|
entity |
| Predicate | hasFishingTargetSpecies |
P45992
|
FINISHED |
| Object | Pacific salmon |
—
|
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: Pacific salmon | Statement: [Kodiak, Alaska, hasFishingTargetSpecies, Pacific salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingTargetSpecies Context triple: [Kodiak, Alaska, hasFishingTargetSpecies, Pacific salmon]
-
A.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
C.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
D.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
E.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.