Triple
T24257631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oficina de Administración de los Tribunales |
E603713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entidad administrativa judicial |
C8184
|
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: entidad administrativa judicial Context triple: [Oficina de Administración de los Tribunales, instanceOf, entidad administrativa judicial]
-
A.
judicial administrative office
chosen
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
B.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
C.
judicial district
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
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.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:05 a.m.