Triple
T27168136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social law division of the Swiss Federal Supreme Court |
E682830
|
entity |
| Predicate | abbreviationOfParentCourt |
P50966
|
FINISHED |
| Object | BGer |
—
|
NE NERFINISHED |
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: BGer | Statement: [Social law division of the Swiss Federal Supreme Court, abbreviationOfParentCourt, BGer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfParentCourt Context triple: [Social law division of the Swiss Federal Supreme Court, abbreviationOfParentCourt, BGer]
-
A.
courtAbbreviation
chosen
Indicates the shortened or abbreviated form of a court’s official name.
-
B.
parentCourt
Indicates that one court is hierarchically above and has authority over another court within a judicial system.
-
C.
respondentAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name or designation of the respondent entity.
-
D.
defendantAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name or designation of a defendant in a legal context.
-
E.
parentAbbreviationExpanded
Indicates that a given expanded term or phrase is the full, non-abbreviated form corresponding to a parent abbreviation.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625451be88190b9b2c24b3d50e09c |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:22 a.m.