Triple
T38395210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Геральдический совет при Президенте Российской Федерации |
E900741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | консультативный орган |
C655
|
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: консультативный орган Context triple: [Геральдический совет при Президенте Российской Федерации, instanceOf, консультативный орган]
-
A.
Vertretungsorgan
A Vertretungsorgan is an authorized representative body or individual within an organization or legal entity that is empowered to act and make binding decisions on its behalf.
-
B.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
C.
órgano de decisión
Un órgano de decisión es una entidad o grupo formalmente constituido dentro de una organización, responsable de analizar información, deliberar y adoptar resoluciones que orientan o determinan su rumbo y funcionamiento.
-
D.
organ of the Assembly of the Republic
An organ of the Assembly of the Republic is an institutional body or structural component within the Assembly that performs specific legislative, administrative, or oversight functions to support its constitutional role.
-
E.
карательный орган
Карательный орган — это государственная или окологосударственная структура, наделённая полномочиями применять репрессивные меры, включая наказания и принуждение, для подавления нарушений установленных норм и поддержания существующего порядка.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.