Triple
T10372268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak Land Forces |
E244411
|
entity |
| Predicate | isProfessionalForce |
P21175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Slovak Land Forces, isProfessionalForce, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProfessionalForce Context triple: [Slovak Land Forces, isProfessionalForce, true]
-
A.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
B.
wasProfessionalSoldier
Indicates that an individual served as a professional soldier, engaging in military service as their primary occupation.
-
C.
isRegularArmyUnit
chosen
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
D.
isVolunteerForce
Indicates that a group or force is composed of individuals who serve voluntarily rather than by conscription or obligation.
-
E.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97ed09c8190a3627aa7b5eea62f |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.