Triple
T32334397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hälsingegårdar region |
E826132
|
entity |
| Predicate | coordinateRegionApprox |
P97139
|
FINISHED |
| Object | 61°N 16°E |
—
|
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: 61°N 16°E | Statement: [Hälsingegårdar region, coordinateRegionApprox, 61°N 16°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateRegionApprox Context triple: [Hälsingegårdar region, coordinateRegionApprox, 61°N 16°E]
-
A.
approximationRegion
chosen
Indicates a region or range within which a value, object, or condition is considered an acceptable approximation of a reference or target.
-
B.
coordinateRegion
Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
-
C.
coordinateRegionWith
Indicates that one entity aligns or harmonizes its regional scope, boundaries, or parameters with those of another entity.
-
D.
coRulerRegion
Indicates a relationship where multiple rulers share governing authority over the same region.
-
E.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:48 a.m.