Triple

T23804755
Position Surface form Disambiguated ID Type / Status
Subject Anglican Bishop of Canberra and Goulburn E589672 entity
Predicate secondaryCityInTitle P114943 FINISHED
Object Goulburn 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: Goulburn | Statement: [Anglican Bishop of Canberra and Goulburn, secondaryCityInTitle, Goulburn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryCityInTitle
Context triple: [Anglican Bishop of Canberra and Goulburn, secondaryCityInTitle, Goulburn]
  • A. secondarySeeCity chosen
    Indicates that an entity has a secondary or less prominent association with a particular city.
  • B. secondMetropolitan
    Indicates that one entity is the second metropolitan (e.g., second-ranking or second-designated metropolitan authority or see) in relation to another entity.
  • C. hasSecondaryCity
    Indicates that an entity possesses or is associated with a secondary city in addition to its primary city.
  • D. secondaryCapital
    Indicates that a location serves as an additional or secondary capital city for a political entity, alongside its primary capital.
  • E. secondaryTo
    Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
  • 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_69e25d19fecc8190a5cf39bbb18d5d7f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c7511db08190aa3eb08f3e3ae515 completed April 29, 2026, 8:54 a.m.
PD Predicate disambiguation batch_69f155fe300481909bd617443228df65 completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:55 p.m.