Triple
T4059040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Kazakhstan |
E84763
|
entity |
| Predicate | standardServiceTerm |
P32858
|
FINISHED |
| Object | 12 months conscription |
—
|
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 conscription | Statement: [Armed Forces of Kazakhstan, standardServiceTerm, 12 months conscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardServiceTerm Context triple: [Armed Forces of Kazakhstan, standardServiceTerm, 12 months conscription]
-
A.
primaryServicePeriod
chosen
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
B.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
D.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
E.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbd13b4481908f9c09cc4f4a9724 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.