Triple

T4888486
Position Surface form Disambiguated ID Type / Status
Subject Azerbaijan Soviet Socialist Republic E109498 entity
Predicate subdivisionTypeInUSSR P9832 FINISHED
Object union republic 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: union republic | Statement: [Azerbaijan Soviet Socialist Republic, subdivisionTypeInUSSR, union republic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeInUSSR
Context triple: [Azerbaijan Soviet Socialist Republic, subdivisionTypeInUSSR, union republic]
  • A. statusInSovietUnion
    Indicates the legal, social, or political standing an entity held within the Soviet Union.
  • B. hasTypeOfSubdivision
    Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
  • C. countrySubdivisionType chosen
    Indicates the specific type or category of an administrative or territorial subdivision within a country (e.g., state, province, region).
  • D. subdividedBy
    Indicates that something is divided into smaller parts or sections by another entity or criterion.
  • E. formerSubdivisionOf
    Indicates that an entity once functioned as an administrative or territorial part of another entity but no longer holds that status.
  • 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_69bd440f71348190b99938e59fb7f9a1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ff981fc819080d4466c6fe06cf3 completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:28 p.m.