Triple
T19638033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakhalin-II |
E471452
|
entity |
| Predicate | seaEnvironment |
P2975
|
FINISHED |
| Object | subarctic |
—
|
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: subarctic | Statement: [Sakhalin-II, seaEnvironment, subarctic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaEnvironment Context triple: [Sakhalin-II, seaEnvironment, subarctic]
-
A.
seaType
Indicates the specific classification or category of a sea associated with an entity.
-
B.
marine
Indicates that an entity is related to, associated with, or located in the sea or ocean environment.
-
C.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
-
D.
marineArea
chosen
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
E.
oceanPresence
Indicates that an entity is located in, adjacent to, or significantly influenced by an ocean.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64107f3fc8190ace6ae67287d280c |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.