Triple
T36779505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian Police and Border Guard Board |
E908728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency of Estonia |
C60053
|
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: government agency of Estonia Context triple: [Estonian Police and Border Guard Board, instanceOf, government agency of Estonia]
-
A.
Estonian organization
chosen
An Estonian organization is a formally or informally structured group based in Estonia that coordinates people and resources to pursue shared goals, such as business, cultural, social, or governmental objectives.
-
B.
Belarusian government agency
A Belarusian government agency is an official public institution established by the state of Belarus to implement specific governmental functions, policies, and administrative tasks within its designated area of responsibility.
-
C.
government agency of Russia
A government agency of Russia is an official state body established by the Russian Federation to implement public policy, administer specific functions, and provide services within a defined area of governance under federal or regional authority.
-
D.
government agency of Poland
A government agency of Poland is an official public institution established by the Polish state to perform specific administrative, regulatory, or service functions on behalf of the government.
-
E.
Swedish government agency
A Swedish government agency is a public organization established by the Swedish state to implement laws, deliver public services, and execute policies under the direction of the government and parliament.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.