Triple
T19609328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Sakhalin Mountains |
E470686
|
entity |
| Predicate | hasCoastlineInfluence |
P136457
|
FINISHED |
| Object | exposed to Pacific storms |
—
|
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: exposed to Pacific storms | Statement: [East Sakhalin Mountains, hasCoastlineInfluence, exposed to Pacific storms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastlineInfluence Context triple: [East Sakhalin Mountains, hasCoastlineInfluence, exposed to Pacific storms]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
influencedCoastlineOf
Indicates that one entity has affected, shaped, or altered the characteristics, form, or condition of another entity’s coastline.
-
C.
hasCoastlineType
Indicates the specific nature or classification of the coastline associated with a geographic entity.
-
D.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
E.
hasCountryCoastline
Indicates that a country possesses a coastline along a sea or ocean.
- F. None of above. chosen
Provenance (4 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640ca57a081909c05000fca52271f |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.