Triple
T31775295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special intervention units |
E811047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian Gendarmerie unit |
C60726
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Romanian Gendarmerie unit Context triple: [Special intervention units, instanceOf, Romanian Gendarmerie unit]
-
A.
subunit of the Romanian Gendarmerie
chosen
A subunit of the Romanian Gendarmerie is an organizational component, such as a company, platoon, or specialized detachment, that performs specific public order, security, or intervention tasks under the command structure of the national gendarmerie.
-
B.
Royal Hungarian Army unit
A Royal Hungarian Army unit is a military formation of the Kingdom of Hungary’s land forces, organized for combat, support, or administrative purposes within the Royal Hungarian Army.
-
C.
branch of the Romanian Armed Forces
A branch of the Romanian Armed Forces is a major organizational component, such as the Land Forces, Air Force, or Naval Forces, responsible for specific types of military operations and capabilities within Romania’s national defense structure.
-
D.
Freikorps unit
A Freikorps unit is a semi-autonomous, often nationalist paramilitary formation composed largely of ex-soldiers, operating with limited state oversight in post–World War I Germany to combat perceived internal and external enemies.
-
E.
Polish military contingent
A Polish military contingent is a temporary, organized group of Polish Armed Forces personnel and resources deployed for specific missions, operations, or international commitments.
- F. None of above.
Provenance (1 batch)
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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:34 p.m.