Triple

T18808761
Position Surface form Disambiguated ID Type / Status
Subject CemAir E459947 entity
Predicate operatesRouteWithinCountry P70721 FINISHED
Object Cape Town–Hoedspruit NE NERFINISHED

How this triple was built (3 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: Cape Town–Hoedspruit | Statement: [CemAir, operatesRouteWithinCountry, Cape Town–Hoedspruit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cape Town–Hoedspruit
Context triple: [CemAir, operatesRouteWithinCountry, Cape Town–Hoedspruit]
  • A. Johannesburg–Hoedspruit
    Johannesburg–Hoedspruit is a domestic air route in South Africa linking the major city of Johannesburg with the safari gateway town of Hoedspruit near Kruger National Park.
  • B. Johannesburg–Kimberley
    Johannesburg–Kimberley is a domestic air route in South Africa connecting the major city of Johannesburg with the historic mining city of Kimberley.
  • C. Cape Town–Johannesburg corridor
    The Cape Town–Johannesburg corridor is a major South African transport and economic axis linking Cape Town and Johannesburg through key road and rail routes that support significant trade and passenger movement.
  • D. Durban–Johannesburg corridor
    The Durban–Johannesburg corridor is a major South African transport and economic artery linking the coastal port city of Durban with the inland metropolis of Johannesburg.
  • E. Maputo Corridor
    The Maputo Corridor is a major regional development and transport route linking South Africa’s industrial heartland to the port city of Maputo in Mozambique, facilitating trade and economic integration in Southern Africa.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Cape Town–Hoedspruit
Target entity description: Cape Town–Hoedspruit is a domestic South African air route linking the coastal city of Cape Town with the safari gateway town of Hoedspruit near Kruger National Park.
  • A. Johannesburg–Hoedspruit
    Johannesburg–Hoedspruit is a domestic air route in South Africa linking the major city of Johannesburg with the safari gateway town of Hoedspruit near Kruger National Park.
  • B. Johannesburg–Kimberley
    Johannesburg–Kimberley is a domestic air route in South Africa connecting the major city of Johannesburg with the historic mining city of Kimberley.
  • C. Cape Town–Johannesburg corridor
    The Cape Town–Johannesburg corridor is a major South African transport and economic axis linking Cape Town and Johannesburg through key road and rail routes that support significant trade and passenger movement.
  • D. Durban–Johannesburg corridor
    The Durban–Johannesburg corridor is a major South African transport and economic artery linking the coastal port city of Durban with the inland metropolis of Johannesburg.
  • E. Maputo Corridor
    The Maputo Corridor is a major regional development and transport route linking South Africa’s industrial heartland to the port city of Maputo in Mozambique, facilitating trade and economic integration in Southern Africa.
  • F. None of above. chosen

Provenance (2 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a3d9c49c8190a9d29a25f0c977b2 completed April 20, 2026, 3:56 a.m.
Created at: April 10, 2026, 11:53 a.m.