Triple
T3515948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Mayen Current |
E74306
|
entity |
| Predicate | coastAlong |
P9306
|
FINISHED |
| Object | eastern coast of Greenland |
—
|
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: eastern coast of Greenland | Statement: [Jan Mayen Current, coastAlong, eastern coast of Greenland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastAlong Context triple: [Jan Mayen Current, coastAlong, eastern coast of Greenland]
-
A.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
B.
flowsAlongCoastOf
chosen
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
C.
coastOff
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
D.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
E.
coastOrientation
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc30362c81908ca7497a6a935cc6 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.