Triple

T22762969
Position Surface form Disambiguated ID Type / Status
Subject Synod of the Diocese of Sydney E563040 entity
Predicate legislativePowerOver P2844 FINISHED
Object diocesan ordinances 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: diocesan ordinances | Statement: [Synod of the Diocese of Sydney, legislativePowerOver, diocesan ordinances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legislativePowerOver
Context triple: [Synod of the Diocese of Sydney, legislativePowerOver, diocesan ordinances]
  • A. hasLegislativePower chosen
    Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
  • B. legislativePowersDerivedFrom
    Indicates that an entity’s authority to make or enact laws originates from, or is granted by, another specified source.
  • C. exercisedPowerOver
    Indicates that one entity exerted control, influence, or authority over another entity.
  • D. hasConcurrentLegislativePowers
    Indicates that two or more governing bodies share the authority to legislate on the same subject matter at the same time.
  • E. legislativeActOf
    Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or 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_69e24552e11c81909c2d61578a558bd7 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17a7dd9348190ba7c74362ad30b1e completed April 29, 2026, 3:26 a.m.
PD Predicate disambiguation batch_69eed2b88d88819096015deb6a648801 completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:26 p.m.