Triple
T21038150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlement of Toulouse |
E518247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sovereign court of justice |
C18604
|
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: sovereign court of justice Context triple: [Parlement of Toulouse, instanceOf, sovereign court of justice]
-
A.
sovereign court
chosen
A sovereign court is the highest judicial body of a sovereign state, vested with ultimate authority to interpret its laws, resolve major legal disputes, and often review the actions of other branches of government.
-
B.
supranational court
A supranational court is a judicial body established by multiple states or international organizations with authority to interpret and apply shared legal norms and issue binding decisions that transcend individual national legal systems.
-
C.
superior court of record
A superior court of record is a higher-level judicial body whose proceedings are formally recorded and preserved, and whose decisions serve as binding legal precedent for lower courts.
-
D.
organ of the International Court of Justice
An organ of the International Court of Justice is an institutional component of the Court, such as the plenary body of judges, chambers, or administrative units, that performs specific judicial or administrative functions essential to the Court’s operation.
-
E.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:05 p.m.