Triple

T31758364
Position Surface form Disambiguated ID Type / Status
Subject University of Sydney By-laws E810612 entity
Predicate haveLegalForceIn P26796 FINISHED
Object New South Wales 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: New South Wales | Statement: [University of Sydney By-laws, haveLegalForceIn, New South Wales]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveLegalForceIn
Context triple: [University of Sydney By-laws, haveLegalForceIn, New South Wales]
  • A. hasLegalForceIn chosen
    Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
  • B. hasLegalForceAs
    Indicates that one thing possesses the binding legal effect or validity in the capacity or role of another specified thing.
  • C. hasLegalForceFrom
    Indicates that one legal instrument, decision, or norm derives its binding legal effect or enforceability from another specified source.
  • D. hasLegalInstrument
    Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
  • E. hasLegalEffect
    Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
  • 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_69f348e340d48190b780fae618c51464 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6ab7ee7248190888c22161b3ce235 completed May 3, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69f6aa21f2508190a204a424ffc00ca6 completed May 3, 2026, 1:51 a.m.
Created at: April 30, 2026, 11:30 p.m.