Triple
T36178587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace of the Court of Justice, Luxembourg |
E1046644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | seat of a supranational court |
C6430
|
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: seat of a supranational court Context triple: [Palace of the Court of Justice, Luxembourg, instanceOf, seat of a supranational court]
-
A.
seat of a supranational parliament
The seat of a supranational parliament is the designated city or complex of buildings where the parliament’s official plenary sessions, administrative functions, and key institutional activities are formally conducted.
-
B.
seat of an international organization
chosen
A seat of an international organization is the city or specific location where the organization’s principal headquarters and core administrative functions are permanently established.
-
C.
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.
-
D.
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.
-
E.
seat of a legislature
The seat of a legislature is the designated city or location where a legislative body officially convenes to conduct its sessions and carry out its formal duties.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.