Triple

T34671333
Position Surface form Disambiguated ID Type / Status
Subject construction troops of the Soviet armed forces E890385 entity
Predicate usedPersonnel P179600 FINISHED
Object conscript soldiers 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: conscript soldiers | Statement: [construction troops of the Soviet armed forces, usedPersonnel, conscript soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedPersonnel
Context triple: [construction troops of the Soviet armed forces, usedPersonnel, conscript soldiers]
  • A. personnel
    Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
  • B. employedPeople
    Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
  • C. authorizedPersonnel
    Indicates that the referenced entity is officially permitted or empowered to access, use, or perform actions within a specified system, resource, or context.
  • D. usedByPerson
    Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
  • E. usedMedicalPersonnel
    Indicates that an entity employed or made use of medical personnel in performing an action or providing a service.
  • 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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722fc90348190966021a1393361bf completed May 3, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69f72157af108190880317a62e634bb0 completed May 3, 2026, 10:20 a.m.
PDg Predicate description generation batch_69f7221bc57c819085c1464a45e61b2f completed May 3, 2026, 10:23 a.m.
Created at: May 1, 2026, 2:05 a.m.