Triple
T26717350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procuraduría General de la Nación |
E673603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | órgano de control disciplinario |
C49080
|
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: órgano de control disciplinario Context triple: [Procuraduría General de la Nación, instanceOf, órgano de control disciplinario]
-
A.
corps de contrôle
chosen
A corps de contrôle is an official body of inspectors or auditors responsible for overseeing, evaluating, and ensuring compliance with laws, regulations, and standards within public or private organizations.
-
B.
карательный орган
Карательный орган — это государственная или окологосударственная структура, наделённая полномочиями применять репрессивные меры, включая наказания и принуждение, для подавления нарушений установленных норм и поддержания существующего порядка.
-
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.
órgano jurídico especializado
Un órgano jurídico especializado es una entidad institucional dotada de competencias técnicas y normativas específicas para interpretar, aplicar o supervisar el cumplimiento del derecho en un ámbito concreto.
-
E.
governance discipline
Governance discipline is the structured set of principles, processes, and practices used to direct, control, and hold an organization accountable in achieving its objectives and managing risks.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:38 a.m.