Triple
T33489635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MO SR |
E857703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slovak public authority |
C12174
|
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: Slovak public authority Context triple: [MO SR, instanceOf, Slovak public authority]
-
A.
Slovak organization
chosen
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.
-
B.
Slovak statute
A Slovak statute is a formal written law enacted by the National Council of the Slovak Republic that regulates specific areas of public or private life within Slovakia’s legal system.
-
C.
Slovenian government body
A Slovenian government body is an official public institution or agency established by the Republic of Slovenia to perform specific administrative, regulatory, legislative, or judicial functions within the national governance framework.
-
D.
Slovak national movement document
A Slovak national movement document is a historical or political text produced by Slovak activists, organizations, or institutions that articulates goals, demands, or ideological foundations related to the assertion and development of Slovak national identity and rights.
-
E.
Slovak person
A Slovak person is an individual who identifies with or holds citizenship of Slovakia, typically sharing its cultural, historical, and linguistic heritage.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.