Triple
T6012524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenai |
E133868
|
entity |
| Predicate | hasFishingResource |
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: [Kenai, hasFishingResource, Pacific salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingResource Context triple: [Kenai, hasFishingResource, 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.
hasMarineResource
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
-
C.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
D.
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.
-
E.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f528acc8190bc6943d812460b57 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.