Triple

T10899448
Position Surface form Disambiguated ID Type / Status
Subject Calder Highway E257398 entity
Predicate passesThrough P225 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: [Calder Highway, passesThrough, Bendigo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bendigo
Context triple: [Calder Highway, passesThrough, 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d761a2392c8190bc2c2359d63eff7a completed April 9, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69e155306e9081909433522eeecf2b7d completed April 16, 2026, 9:31 p.m.
Created at: April 8, 2026, 9:21 p.m.