Triple
T38289958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian–Russian Pomor trade region |
E1022329
|
entity |
| Predicate | mainNorwegianArea |
P125625
|
FINISHED |
| Object | Finnmark |
—
|
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: Finnmark | Statement: [Norwegian–Russian Pomor trade region, mainNorwegianArea, Finnmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainNorwegianArea Context triple: [Norwegian–Russian Pomor trade region, mainNorwegianArea, Finnmark]
-
A.
rankInNorwayByArea
Indicates the position of an entity in an ordered list of areas within Norway, based on its size relative to others.
-
B.
territoryRetainedByNorway
Indicates that a specified territory remains under the control, sovereignty, or possession of Norway.
-
C.
isInFylke
chosen
Indicates that one entity (typically a place or municipality) is located within a specific Norwegian county (fylke).
-
D.
nearCityOnNorwegianSide
Indicates that one entity is located close to a specified city that lies on the Norwegian side of a border or region.
-
E.
hasNordicArea
Indicates that an entity possesses, includes, or is associated with a geographic area located in the Nordic region.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.