Triple
T14524924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 freeway |
E340750
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Bloemfontein |
E24732
|
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: Bloemfontein | Statement: [N1 freeway, connectsCity, Bloemfontein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bloemfontein Context triple: [N1 freeway, connectsCity, Bloemfontein]
-
A.
Bloemfontein
chosen
Bloemfontein is a major South African city known as the seat of the country’s highest courts and one of its three national capitals.
-
B.
Potchefstroom
Potchefstroom is a historic university town in South Africa known for its academic institutions, military base, and role in the North West province’s agriculture and industry.
-
C.
Pietersburg
Pietersburg is the former name of Polokwane, a major city and administrative center in South Africa’s Limpopo province.
-
D.
Witbank
Witbank is a South African coal-mining city in Mpumalanga province, now officially known as Emalahleni.
-
E.
Kroonstad
Kroonstad is a town in the Free State province of South Africa, known as an agricultural and transport hub along the Vaal River.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea04f16f88190ba357b0f8021b46b |
completed | April 14, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe729c439481909dac86ed6f5d6411 |
completed | May 8, 2026, 11:32 p.m. |
Created at: April 10, 2026, 1:22 a.m.