Triple
T25672415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skagen |
E643713
|
entity |
| Predicate | seaConfluence |
P42198
|
FINISHED |
| Object | Skagerrak |
—
|
NE NERFINISHED |
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: Skagerrak | Statement: [Skagen, seaConfluence, Skagerrak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaConfluence Context triple: [Skagen, seaConfluence, Skagerrak]
-
A.
seaConnection
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
B.
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.
-
C.
seaRepresents
Indicates that one entity serves as a symbolic, visual, or conceptual representation of another within a maritime or sea-related context.
-
D.
endSea
chosen
Indicates that something marks the boundary or termination point of a sea or sea area.
-
E.
seaType
Indicates the specific classification or category of a sea associated with an entity.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3389ac819092997022ed2bc2f8 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 7:30 p.m.