Triple
T25920824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Charles Foreland |
E653164
|
entity |
| Predicate | offCoastDirection |
P15643
|
FINISHED |
| Object | west coast of Spitsbergen |
—
|
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: west coast of Spitsbergen | Statement: [Prince Charles Foreland, offCoastDirection, west coast of Spitsbergen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offCoastDirection Context triple: [Prince Charles Foreland, offCoastDirection, west coast of Spitsbergen]
-
A.
coastOrientation
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
B.
coastOff
chosen
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
C.
oceanOrientation
Indicates the directional alignment or facing of something relative to an ocean.
-
D.
seaOrientation
Indicates the directional relationship of something relative to the sea or coastline (e.g., which way it faces or is aligned).
-
E.
departureDirection
Indicates the direction or bearing in which an entity moves away from its point of origin or starting location.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603e97750819094072a118a60e332 |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:32 a.m.