Triple
T2691851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Armed Forces |
E58418
|
entity |
| Predicate | conscriptionTerm |
P41079
|
FINISHED |
| Object | 12 months |
—
|
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: 12 months | Statement: [Russian Armed Forces, conscriptionTerm, 12 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conscriptionTerm Context triple: [Russian Armed Forces, conscriptionTerm, 12 months]
-
A.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
B.
conscriptionAppliesTo
Indicates that mandatory military service requirements are imposed on, or are applicable to, a particular person or group.
-
C.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
D.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
-
E.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0cb9b48190ab354c277cef9e23 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd879bb808190bd2c34de1664c816 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.