Triple

T9121975
Position Surface form Disambiguated ID Type / Status
Subject N11 E218874 entity
Predicate terminus P388 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: [N11, terminus, Ladysmith]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ladysmith
Context triple: [N11, terminus, 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. Lobamba
    Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
  • D. Belhar
    Belhar is a suburb of Cape Town, South Africa, historically significant in the anti-apartheid struggle and as the birthplace of the Belhar Confession.
  • E. Kommetjie
    Kommetjie is a small coastal village on South Africa’s Cape Peninsula known for its surf breaks, long white beaches, and relaxed seaside atmosphere.
  • 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_69ca83dddd548190983b96c664f7f367 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8b46dac8190bde88205c85f596a completed April 1, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0b194f6e48190ae7e9afa4e2cc912 completed April 4, 2026, 6:37 a.m.
Created at: March 30, 2026, 7:17 p.m.