Triple

T7657405
Position Surface form Disambiguated ID Type / Status
Subject BGE (Bundesgerichtsentscheide) E173419 entity
Predicate hasLevelOfCourt P71353 FINISHED
Object court of last instance in Switzerland 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: court of last instance in Switzerland | Statement: [BGE (Bundesgerichtsentscheide), hasLevelOfCourt, court of last instance in Switzerland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLevelOfCourt
Context triple: [BGE (Bundesgerichtsentscheide), hasLevelOfCourt, court of last instance in Switzerland]
  • A. hadCourtLevel chosen
    Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
  • B. hasTypeOfCourt
    Indicates that an entity is associated with or classified by a specific type or category of court.
  • C. hasLowerCourt
    Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
  • D. hasCourts
    Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
  • E. hasSeniorCourt
    Indicates that one court is hierarchically subordinate to another court that serves as its senior or higher-level authority.
  • 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_69c69955517c819085bc715b96d304d2 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7061cbc3c8190a917dd7e71214182 completed March 27, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69c7015dd8fc8190bc5f52a12bd46209 completed March 27, 2026, 10:14 p.m.
Created at: March 27, 2026, 3:59 p.m.