Triple

T5061315
Position Surface form Disambiguated ID Type / Status
Subject Bellingen E114027 entity
Predicate near P350 FINISHED
Object Urunga E129685 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: Urunga | Statement: [Bellingen, near, Urunga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urunga
Context triple: [Bellingen, near, Urunga]
  • A. Urunga chosen
    Urunga is a small coastal town in New South Wales, Australia, known for its scenic boardwalks, estuary views, and relaxed seaside atmosphere.
  • B. Gundunguri
    Gundunguri is an alternative name for the Gundungurra, an Aboriginal Australian people traditionally associated with the Southern Highlands and Blue Mountains region of New South Wales.
  • C. Urakhi
    Urakhi is a dialect of the Dargin language spoken by a subset of the Dargin people in the North Caucasus region of Russia.
  • D. Karanga
    Karanga is a major dialect of the Shona language spoken primarily in southern Zimbabwe, known for its distinct phonological and lexical features.
  • E. Ushguli
    Ushguli is a remote highland village community in Georgia’s Svaneti region, renowned for its medieval stone towers, well-preserved Svan culture, and status as one of the highest continuously inhabited settlements in Europe.
  • 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_69bd443c0c8c81908663b77afb28e165 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd74740ae08190930f1fd57187334e completed March 20, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea49566548190bc6328996789ad9f completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:38 p.m.