Triple

T6791310
Position Surface form Disambiguated ID Type / Status
Subject Inkeri E155937 entity
Predicate traditionalAreaIn P59512 FINISHED
Object northwestern Russia 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: northwestern Russia | Statement: [Inkeri, traditionalAreaIn, northwestern Russia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalAreaIn
Context triple: [Inkeri, traditionalAreaIn, northwestern Russia]
  • A. traditionalDistrict
    Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary administrative or cultural district.
  • B. traditionalSettlementArea chosen
    Indicates that an area is recognized as a traditional settlement zone associated with a particular group or community.
  • C. traditionalHousingRegion
    Indicates the region where a group’s customary or historically established housing patterns are typically found.
  • D. traditionalCountry
    Indicates that a country is characterized by long-established customs, cultural practices, and social norms that have been preserved over time.
  • E. traditionalSubdivisionOf
    Indicates that one entity is a historically or culturally recognized sub-unit or component region of another, according to traditional (rather than strictly modern administrative) divisions.
  • 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_69c6881770fc8190972b2906390380f5 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2acbfc0819081f2d6cebfb91765 completed March 27, 2026, 6:55 p.m.
PD Predicate disambiguation batch_69c6d0979ce0819094678896da4e3169 completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:15 p.m.