Triple
T13654012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellville |
E326809
|
entity |
| Predicate | nearbyArea |
P2064
|
FINISHED |
| Object | Parow |
E633628
|
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: Parow | Statement: [Bellville, nearbyArea, Parow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parow Context triple: [Bellville, nearbyArea, Parow]
-
A.
Parow
chosen
Parow is a suburb of Cape Town in the Western Cape, South Africa, known as a residential and commercial area within the greater Cape Town metropolitan region.
-
B.
Paravaqar
Paravaqar is a small town located in Armenia's northeastern Tavush Province, known for its rural setting and proximity to forested, mountainous landscapes.
-
C.
Parushni
Parushni is the ancient Vedic name for the Ravi River, one of the major rivers of the northwestern Indian subcontinent.
-
D.
Porul
Porul is the second section of the ancient Tamil classic Tirukkural, focusing on ethics, governance, politics, and social conduct.
-
E.
Pewelka
Pewelka is a village in southern Poland located within the administrative district of Gmina Stryszawa in Lesser Poland Voivodeship.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b03083c8190855a2a4ee44e4098 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:52 p.m.