Triple

T16513024
Position Surface form Disambiguated ID Type / Status
Subject Armed Forces of Uzbekistan E401109 entity
Predicate legalFormedFrom P16540 FINISHED
Object Soviet Armed Forces units in the Uzbek SSR 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: Soviet Armed Forces units in the Uzbek SSR | Statement: [Armed Forces of Uzbekistan, legalFormedFrom, Soviet Armed Forces units in the Uzbek SSR]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalFormedFrom
Context triple: [Armed Forces of Uzbekistan, legalFormedFrom, Soviet Armed Forces units in the Uzbek SSR]
  • A. legalFormedAs
    Indicates that an entity was established or constituted under a specific legal structure or organizational form.
  • B. divisionFormedFrom chosen
    Indicates that an organizational division was created by splitting off from or being reorganized out of another existing entity.
  • C. underlyingCompanyFormedBy
    Indicates that an underlying company was created, established, or formed by a specified entity.
  • D. issuerFormationMethod
    Indicates the method or process by which an issuer was created or legally formed.
  • E. foundedByMergerOf
    Indicates that an entity was created through the merger or combination of two or more predecessor entities.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e78d4848190a55de9902115b1b2 completed April 18, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69e296995d388190b88ebe189dce890d completed April 17, 2026, 8:22 p.m.
Created at: April 10, 2026, 5:14 a.m.