Triple

T34526466
Position Surface form Disambiguated ID Type / Status
Subject Magistrates Court of Western Australia E886411 entity
Predicate hasJudicialOfficers P55584 FINISHED
Object magistrates 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: magistrates | Statement: [Magistrates Court of Western Australia, hasJudicialOfficers, magistrates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJudicialOfficers
Context triple: [Magistrates Court of Western Australia, hasJudicialOfficers, magistrates]
  • A. hasJudicialOfficer chosen
    Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
  • B. hasJudiciary
    Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
  • C. hasMagistrateJudges
    Indicates that one legal jurisdiction, court, or governing body includes or is served by one or more magistrate judges.
  • D. hasJudges
    Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
  • E. hasJudge
    Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
  • 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_69f349cd7c148190aa99192b126d1527 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234bcaa48190ac970759d34e254a completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:02 a.m.