Triple
T29680179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Armed Forces |
E750928
|
entity |
| Predicate | alternativeCivilServiceAvailable |
P52738
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Austrian Armed Forces, alternativeCivilServiceAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeCivilServiceAvailable Context triple: [Austrian Armed Forces, alternativeCivilServiceAvailable, yes]
-
A.
positionOnCivilService
Indicates the role, rank, or status an individual holds within a civil service system.
-
B.
allowsCivilianService
chosen
Indicates that an authority permits individuals to perform an alternative form of civilian service instead of regular military service.
-
C.
civilianEligibility
Indicates that an entity meets the criteria or conditions required to be classified or treated as a civilian in a given context.
-
D.
civilOrMilitary
Indicates that something is classified as either civil (non-military) or military in nature or function.
-
E.
nationalService
Indicates that an entity performs or is obligated to perform service duties on behalf of a nation, typically in a governmental, military, or civic capacity.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 7:09 p.m.