Triple

T234951
Position Surface form Disambiguated ID Type / Status
Subject Melbourne E4488 entity
Predicate hasNickname P39 FINISHED
Object Melbs 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: Melbs | Statement: [Melbourne, hasNickname, Melbs]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Melbs
Context triple: [Melbourne, hasNickname, Melbs]
  • A. 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.
  • B. Sydney
    Sydney is Australia's largest and most populous city, renowned for its iconic harbour, Opera House, and Harbour Bridge.
  • C. Adelaide
    Adelaide is the coastal capital city of South Australia, known for its festivals, wine regions, and planned grid layout.
  • D. Brisbane
    Brisbane is the capital and most populous city of the Australian state of Queensland, known for its subtropical climate, riverfront setting, and role as a major economic and cultural hub.
  • E. Perth
    Perth is a historic city in central Scotland, often called the "Fair City," known for its medieval heritage and role as a former Scottish capital.
  • 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_69a257363ffc81909757bde7ab3404da completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25cc9ab2c81909af278a07f86aa1e completed Feb. 28, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3673474548190aea1f43318d15a71 completed Feb. 28, 2026, 10:07 p.m.
Created at: Feb. 28, 2026, 2:53 a.m.