Triple

T12744322
Position Surface form Disambiguated ID Type / Status
Subject Meyerton E304565 entity
Predicate locatedNear P294 FINISHED
Object Vereeniging E24651 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: Vereeniging | Statement: [Meyerton, locatedNear, Vereeniging]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vereeniging
Context triple: [Meyerton, locatedNear, Vereeniging]
  • A. Vereeniging chosen
    Vereeniging is a South African town in Gauteng province best known historically as the site where the Treaty of Vereeniging ended the Second Boer War in 1902.
  • B. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • C. Wilrijk
    Wilrijk is a southern district of the Belgian city of Antwerp, known for its residential character and green spaces.
  • D. Hillegom
    Hillegom is a town in the western Netherlands known for its flower bulb cultivation and location within the historic Duin- en Bollenstreek (Dune and Bulb Region).
  • E. Utrecht Overvecht
    Utrecht Overvecht is a suburban railway station in the Overvecht district of Utrecht in the Netherlands, serving as a local commuter hub.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd42fe08190a85467b1a998d2af completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c94265481908ace9cac757df890 completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:26 p.m.