Triple

T14545862
Position Surface form Disambiguated ID Type / Status
Subject Hume corridor E341289 entity
Predicate connects P390 FINISHED
Object Melbourne E4488 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: Melbourne | Statement: [Hume corridor, connects, Melbourne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Melbourne
Context triple: [Hume corridor, connects, Melbourne]
  • A. Melbourne
    Melbourne is a coastal city in east-central Florida known for its beaches, aerospace and technology industries, and role as a commercial and cultural hub of the Space Coast.
  • B. Melbourne chosen
    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. Sydney
    Sydney is Australia's largest and most populous city, renowned for its iconic harbour, Opera House, and Harbour Bridge.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb1bfc2b48190adb0897682c26a9a completed April 14, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda9107e9c8190850716c21e627a39 completed May 8, 2026, 9:12 a.m.
Created at: April 10, 2026, 1:22 a.m.