Triple
T17087517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koyuk, Alaska |
E414636
|
entity |
| Predicate | hasKeyNaturalResource |
P2856
|
FINISHED |
| Object | marine mammals |
—
|
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: marine mammals | Statement: [Koyuk, Alaska, hasKeyNaturalResource, marine mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyNaturalResource Context triple: [Koyuk, Alaska, hasKeyNaturalResource, marine mammals]
-
A.
hasNaturalResourceRoute
Indicates that there is a route or pathway used for the transport or access of natural resources between entities.
-
B.
usesNaturalResource
Indicates that an entity makes use of a natural resource (such as water, minerals, or forests) to support its activities, processes, or functions.
-
C.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
D.
naturalResources
chosen
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
E.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.