Triple

T8315001
Position Surface form Disambiguated ID Type / Status
Subject Federal Labour Court of Germany E194683 entity
Predicate hearsCasesInLastInstance P81880 FINISHED
Object yes 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: yes | Statement: [Federal Labour Court of Germany, hearsCasesInLastInstance, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hearsCasesInLastInstance
Context triple: [Federal Labour Court of Germany, hearsCasesInLastInstance, yes]
  • A. hearsCasesAgainst
    Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
  • B. hearsCasesUnder
    Indicates that a judicial body or authority has the responsibility and power to adjudicate legal cases falling within a specified jurisdiction, category, or scope.
  • C. hearsCasesBetween
    Indicates that a judicial body or authority formally considers and adjudicates legal disputes involving two or more parties.
  • D. hasCourtInEach
    Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
  • E. laterCourt
    Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
  • F. None of above. chosen

Provenance (4 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_69ca82e6e2648190a31eaf6f4f757b2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7f540b2081908ccb1b2ed040c74e completed March 31, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69cb70bf689c8190a9d9b6b872abf53d completed March 31, 2026, 6:59 a.m.
PDg Predicate description generation batch_69cb77690720819099de1e22b84a9563 completed March 31, 2026, 7:27 a.m.
Created at: March 30, 2026, 5:55 p.m.