Triple

T3708104
Position Surface form Disambiguated ID Type / Status
Subject Imperial Russian administrative system E80940 entity
Predicate includedSpecialRegionType P50933 FINISHED
Object oblast 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: oblast | Statement: [Imperial Russian administrative system, includedSpecialRegionType, oblast]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includedSpecialRegionType
Context triple: [Imperial Russian administrative system, includedSpecialRegionType, oblast]
  • A. includedTerritoryType
    Indicates that one territory type is contained within, or forms part of, another territory type.
  • B. regionSpecialization
    Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
  • C. eligibleRegion
    Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
  • D. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • E. excludesRegion
    Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
  • F. None of above. chosen

Provenance (4 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_69ad8b1793888190a5f70e4b21dc05a1 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc580b08481908391283778d5ce14 completed March 8, 2026, 6:52 p.m.
PD Predicate disambiguation batch_69adc041a8608190a2d543dab6d2ef6c completed March 8, 2026, 6:30 p.m.
PDg Predicate description generation batch_69adc133ef50819094c2b971f31f1615 completed March 8, 2026, 6:34 p.m.
Created at: March 8, 2026, 3:33 p.m.