Triple
T1837283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Army |
E41092
|
entity |
| Predicate | reintroducedConscription |
P18106
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Swedish Army, reintroducedConscription, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintroducedConscription Context triple: [Swedish Army, reintroducedConscription, 2017]
-
A.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
B.
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.
-
C.
conscriptionAppliesTo
Indicates that mandatory military service requirements are imposed on, or are applicable to, a particular person or group.
-
D.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
E.
recommissioned
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.