Triple

T2014151
Position Surface form Disambiguated ID Type / Status
Subject Estcourt E43755 entity
Predicate nearbyCity P350 FINISHED
Object Ladysmith E42617 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: Ladysmith | Statement: [Estcourt, nearbyCity, Ladysmith]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ladysmith
Context triple: [Estcourt, nearbyCity, Ladysmith]
  • A. Ladysmith chosen
    Ladysmith is a South African town in KwaZulu-Natal best known as a key site of the Second Boer War, particularly the famous Siege of Ladysmith.
  • B. Ladysmith
    Ladysmith is a small coastal town on Vancouver Island in British Columbia, Canada, known for its historic downtown and scenic harbor.
  • C. Mabalako
    Mabalako is a health zone in North Kivu Province in the eastern Democratic Republic of the Congo, known for being heavily affected by Ebola outbreaks.
  • D. Samtskhe
    Samtskhe is a historical and geographic region in southern Georgia known for its mountainous landscapes, medieval fortresses, and cultural heritage.
  • E. Soshanguve
    Soshanguve is a large township in the northern part of the Gauteng province of South Africa, known for its diverse population and proximity to Pretoria.
  • 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_69a88716e9f08190946313fdc949e3cf completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb8b42d508190bf2b63132bb2ad77 completed March 7, 2026, 5:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0aeca6388190befe0630d44de109 completed March 8, 2026, 11:49 p.m.
Created at: March 4, 2026, 7:37 p.m.