Triple
T29009270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Azerbaijan |
E736517
|
entity |
| Predicate | hasConscriptionTerm |
P41079
|
FINISHED |
| Object | 18 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: 18 months | Statement: [Armed Forces of Azerbaijan, hasConscriptionTerm, 18 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConscriptionTerm Context triple: [Armed Forces of Azerbaijan, hasConscriptionTerm, 18 months]
-
A.
conscriptionTerm
chosen
Indicates the length or duration of mandatory military service imposed on individuals.
-
B.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
C.
conscriptionAppliesTo
Indicates that mandatory military service requirements are imposed on, or are applicable to, a particular person or group.
-
D.
hadMilitaryObligationsTo
Indicates that one party was bound by duty or law to provide military service, support, or protection to another party.
-
E.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: April 28, 2026, 9:41 a.m.