Triple
T31216457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Staff of the Slovenian Armed Forces |
E795883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slovenian government body |
C57420
|
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: Slovenian government body Context triple: [General Staff of the Slovenian Armed Forces, instanceOf, Slovenian government body]
-
A.
Slovene-American organization
A Slovene-American organization is a group that promotes cultural, social, and sometimes economic ties between people of Slovene heritage and the broader American community through events, advocacy, and support services.
-
B.
Slovenian statute
A Slovenian statute is a formal written law enacted by the legislative authority of Slovenia that establishes, modifies, or regulates legal rights and obligations within the country’s jurisdiction.
-
C.
Slovak organization
A Slovak organization is an entity legally established or operating in Slovakia, such as a company, institution, association, or non-profit, that pursues specific economic, social, cultural, or public-interest objectives within the Slovak legal and regulatory framework.
-
D.
Ukrainian government body
A Ukrainian government body is an official public institution established by the state of Ukraine to exercise specific executive, legislative, judicial, or administrative functions in accordance with national law.
-
E.
Slovenian person
A Slovenian person is an individual who is a citizen or native of Slovenia, typically sharing in its South Slavic cultural, historical, and linguistic heritage.
- F. None of above. chosen
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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.