Triple
T15889720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harstad harbour |
E385283
|
entity |
| Predicate | locatedInLatitudeRange |
P13005
|
FINISHED |
| Object | high northern latitudes |
—
|
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: high northern latitudes | Statement: [Harstad harbour, locatedInLatitudeRange, high northern latitudes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLatitudeRange Context triple: [Harstad harbour, locatedInLatitudeRange, high northern latitudes]
-
A.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
C.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
D.
notVisibleFromLatitudesNorthOf
Indicates that the subject cannot be seen or observed from any location situated at latitudes north of the specified reference latitude.
-
E.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.