Triple

T12211940
Position Surface form Disambiguated ID Type / Status
Subject Greater Johannesburg metropolitan area E290983 entity
Predicate contains P35 FINISHED
Object Alberton E267317 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: Alberton | Statement: [Greater Johannesburg metropolitan area, contains, Alberton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alberton
Context triple: [Greater Johannesburg metropolitan area, contains, Alberton]
  • A. Alberton
    Alberton is an inner north-western suburb of Adelaide, South Australia, historically known as the traditional home of the Port Adelaide Football Club.
  • B. Alberton chosen
    Alberton is a town in the East Rand region of Gauteng, South Africa, forming part of the greater Johannesburg metropolitan area.
  • C. Alberton
    Alberton is a small rural township located within Ontario’s Rainy River District in Canada.
  • D. Alloa
    Alloa is a town in central Scotland that serves as the main commercial and population hub of Clackmannanshire.
  • E. Dumbarton
    Dumbarton is a historic Scottish town on the River Clyde known for its prominent role in shipbuilding and maritime industry.
  • 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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91c915f548190b34a743f0a3bb51a completed April 10, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b873c308190a2c1d02723cfa2e9 completed May 2, 2026, 7:07 p.m.
Created at: April 8, 2026, 9:51 p.m.