Triple
T29302792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contentious-Administrative Courts |
E743005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish judicial body |
C48549
|
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: Spanish judicial body Context triple: [Contentious-Administrative Courts, instanceOf, Spanish judicial body]
-
A.
Spanish court
chosen
A Spanish court is a judicial body within Spain’s legal system responsible for interpreting and applying the law, resolving disputes, and administering justice in accordance with Spanish legislation and constitutional principles.
-
B.
High Court of Justice of Spain
The High Court of Justice of Spain is the highest judicial body within each autonomous community, responsible for overseeing the administration of justice in its territory and serving as the final appellate court for most regional matters.
-
C.
Spanish government agency
A Spanish government agency is a public organization established by Spain’s national, regional, or local authorities to implement laws, deliver public services, and manage specific administrative functions within the country.
-
D.
Spanish legal act
A Spanish legal act is a formal, binding provision or decision issued by a competent authority within Spain’s legal system that creates, modifies, or extinguishes rights and obligations under Spanish law.
-
E.
Spanish state institution
A Spanish state institution is a public organization established and governed by the Spanish government to perform official administrative, regulatory, social, or cultural functions within the state.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:11 p.m.