Triple
T11414745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian Armed Forces |
E270460
|
entity |
| Predicate | conscriptionReintroduced |
P18106
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Lithuanian Armed Forces, conscriptionReintroduced, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conscriptionReintroduced Context triple: [Lithuanian Armed Forces, conscriptionReintroduced, 2015]
-
A.
conscriptionTerm
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.
reintroduced
chosen
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
E.
musteredIntoService
Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801ae47d0819098123505309c4a68 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.