Triple

T3545472
Position Surface form Disambiguated ID Type / Status
Subject Goulburn E74985 entity
Predicate hasRailConnectionTo P848 FINISHED
Object Sydney E8462 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: Sydney | Statement: [Goulburn, hasRailConnectionTo, Sydney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sydney
Context triple: [Goulburn, hasRailConnectionTo, Sydney]
  • A. Sydney chosen
    Sydney is Australia's largest and most populous city, renowned for its iconic harbour, Opera House, and Harbour Bridge.
  • B. Melbourne
    Melbourne is a major Australian city known for its vibrant arts scene, diverse culture, and status as a leading center for sports and education.
  • C. Melbourne
    Melbourne is a historic market town in Derbyshire, England, known for its Georgian architecture and the notable Melbourne Hall and gardens.
  • D. Melbourn
    Melbourn is a village and civil parish in South Cambridgeshire, England, known for its historic architecture and rural community character.
  • E. Brisbane
    Brisbane is a small city in northern San Mateo County, California, located just south of San Francisco on the lower slopes of San Bruno Mountain.
  • 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_69ad85d274cc8190ab59c97298a1cfbf completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbf77d938819095c72a88b5af644a completed March 8, 2026, 6:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb6f45ec8190835a8a68ffa99efc completed March 13, 2026, 7:23 a.m.
Created at: March 8, 2026, 3:20 p.m.