Triple
T26489980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendsyssel-Thy |
E669128
|
entity |
| Predicate | northernTip |
P156687
|
FINISHED |
| Object | Skagen Odde |
—
|
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: Skagen Odde | Statement: [Vendsyssel-Thy, northernTip, Skagen Odde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTip Context triple: [Vendsyssel-Thy, northernTip, Skagen Odde]
-
A.
isOnNorthernTipOf
chosen
Indicates that one entity is located at or forms the northernmost extremity or tip of another entity.
-
B.
northernBranch
Indicates that one entity functions as the northern division, section, or offshoot of another entity.
-
C.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
D.
northernShore
Indicates that one entity is located on the northern shore or northern side of another entity, typically a body of water or coastline.
-
E.
northTerminusType
Indicates the type or nature of the northern endpoint or terminus of a route, line, or similar linear feature.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61302356c8190b8dc90949fdff41b |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:03 a.m.