Triple

T6850029
Position Surface form Disambiguated ID Type / Status
Subject Central Victoria E157991 entity
Predicate hasNotableCity P2813 FINISHED
Object Bendigo E159590 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: Bendigo | Statement: [Central Victoria, hasNotableCity, Bendigo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bendigo
Context triple: [Central Victoria, hasNotableCity, Bendigo]
  • A. Bendigo chosen
    Bendigo is a historic regional city in central Victoria, Australia, known for its 19th-century gold rush heritage and well-preserved Victorian architecture.
  • B. Ballarat
    Ballarat is a historic regional city in central Victoria, Australia, best known for its 19th-century gold rush heritage and well-preserved Victorian-era architecture.
  • C. Geelong
    Geelong is a coastal city in the state of Victoria, Australia, known as a major regional center southwest of Melbourne.
  • D. Albury
    Albury is a small rural village and civil parish in Hertfordshire, England, known for its historic church and countryside setting.
  • E. Albury
    Albury is a major regional city in New South Wales, Australia, located on the border with Victoria and known as a key commercial and transport hub of the Murray River region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6882fae988190864cbba788c5ebb4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d84c45708190918adfc028252400 completed March 27, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72fcdf3888190b95b2ce10964793b completed March 28, 2026, 1:33 a.m.
Created at: March 27, 2026, 2:20 p.m.