Triple
T26954462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ångermanland |
E678858
|
entity |
| Predicate | hasCountyOverlapWith |
P93335
|
FINISHED |
| Object | Västernorrland County |
—
|
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: Västernorrland County | Statement: [Ångermanland, hasCountyOverlapWith, Västernorrland County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyOverlapWith Context triple: [Ångermanland, hasCountyOverlapWith, Västernorrland County]
-
A.
hasJurisdictionOverlapWith
Indicates that two authorities or entities share some portion of legal or regulatory control over the same area, subject, or set of activities.
-
B.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
-
C.
geographicOverlap
chosen
Indicates that two geographic areas share at least part of the same physical space or territory.
-
D.
hasNearbyCounty
Indicates that one county is geographically close to or directly adjacent to another county.
-
E.
hasAdditionalCounty
Indicates that an entity is associated with one or more counties beyond its primary or originally specified county.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 27, 2026, 6:26 a.m.