Triple
T14122938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Denmark |
E339946
|
entity |
| Predicate | maySitInEnlargedPanelOf |
P4504
|
FINISHED |
| Object | 7 judges |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 7 judges | Statement: [Supreme Court of Denmark, maySitInEnlargedPanelOf, 7 judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySitInEnlargedPanelOf Context triple: [Supreme Court of Denmark, maySitInEnlargedPanelOf, 7 judges]
-
A.
maySitAs
Indicates that one entity is permitted or authorized to serve or participate in an official capacity within another entity (such as a body, panel, or role).
-
B.
maySitEnBanc
chosen
Indicates that a judicial body has the authority or option to convene and hear a case with all (or a large majority of) its judges sitting together as a full court.
-
C.
maySitByRight
Indicates that an entity has the right or permission to sit next to another entity.
-
D.
canBeChairOf
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
-
E.
maySitWith
Indicates that one entity is permitted or allowed to sit together with another entity.
- F. None of above.
Provenance (3 batches)
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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6095548881908a9e66adccca92d2 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.