Triple

T30610709
Position Surface form Disambiguated ID Type / Status
Subject Advocate Depute E779170 entity
Predicate typicalCourt P186238 FINISHED
Object High Court of Justiciary E23940 NE 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: High Court of Justiciary | Statement: [Advocate Depute, typicalCourt, High Court of Justiciary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalCourt
Context triple: [Advocate Depute, typicalCourt, High Court of Justiciary]
  • A. traditionalCourt
    Indicates that an entity is associated with or takes place in a conventional or historically established court of law, as opposed to a modern, alternative, or informal judicial setting.
  • B. courtOf chosen
    Indicates that one entity serves as the judicial body or tribunal associated with, or having jurisdiction over, another entity.
  • C. practiceCourt
    Indicates that an entity uses or is associated with a particular court for practice or training activities.
  • D. courts
    Indicates that one entity actively seeks the favor, support, or romantic interest of another through deliberate actions or overtures.
  • E. trialCourt
    Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
  • F. None of above.

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_69f224a21fc08190abd9d8dd9eb6bb4c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2863de1d288190a6bf2137784604f1 completed June 9, 2026, 7:05 p.m.
PD Predicate disambiguation batch_6a0379e2fac0819089b522db3260028c completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 8:26 p.m.