Triple

T12447873
Position Surface form Disambiguated ID Type / Status
Subject Kota Kinabalu E297449 entity
Predicate hasFormerName P65 FINISHED
Object Jesselton E297449 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: Jesselton | Statement: [Kota Kinabalu, hasFormerName, Jesselton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jesselton
Context triple: [Kota Kinabalu, hasFormerName, Jesselton]
  • A. Jesselton chosen
    Jesselton is the former colonial-era name of Kota Kinabalu, the capital city of Sabah in Malaysian Borneo.
  • B. Loxton
    Loxton is a rural town in South Australia's Riverland region, known for its irrigated agriculture, particularly citrus and grape production, and its location along the Murray River.
  • C. Springston
    Springston is a small rural township in New Zealand’s Canterbury region, located within the Selwyn District near Christchurch.
  • D. Fullarton
    Fullarton is a Scottish surname historically associated with families from the Ayrshire region of Scotland.
  • E. Lockington
    Lockington is a small rural town in northern Victoria, Australia, known for its agricultural community and historic railway heritage.
  • 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_69d6ada166c48190b902972cd2408fa3 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d9e592c81908cf7f3ca170d942c completed April 10, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b9f4dd08190b1d62b03d68cc8a6 completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:56 p.m.