Triple
T38289960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian–Russian Pomor trade region |
E1022329
|
entity |
| Predicate | mainRussianArea |
P127825
|
FINISHED |
| Object | Arkhangelsk region |
—
|
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: Arkhangelsk region | Statement: [Norwegian–Russian Pomor trade region, mainRussianArea, Arkhangelsk region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRussianArea Context triple: [Norwegian–Russian Pomor trade region, mainRussianArea, Arkhangelsk region]
-
A.
leftRussia
Indicates that an entity departed from or ceased to be in Russia.
-
B.
locatedInRegionOfRussia
chosen
Indicates that one entity is geographically situated within a specified region of Russia.
-
C.
rankInRussiaByArea
Indicates the position of an entity in an ordered list of entities in Russia sorted by their area size.
-
D.
partOfUnderRussianAdministration
Indicates that one entity is a territorial or administrative subdivision that is currently governed or controlled by Russian authorities.
-
E.
largestMunicipalityByArea
Indicates that the subject is the municipality with the greatest land area within the specified region or set of municipalities.
- 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.