Triple
T13689103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paarl Rock |
E328213
|
entity |
| Predicate | overlooks |
P1323
|
FINISHED |
| Object | Paarl |
E64645
|
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: Paarl | Statement: [Paarl Rock, overlooks, Paarl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paarl Context triple: [Paarl Rock, overlooks, Paarl]
-
A.
Paarl
chosen
Paarl is a historic town in South Africa renowned for its wine estates, scenic granite rock formations, and role in the development of the Afrikaans language.
-
B.
Durbanville
Durbanville is a suburban town in the northern outskirts of Cape Town, South Africa, known for its wine estates and residential character.
-
C.
Uitenhage
Uitenhage is a South African town in the Eastern Cape known historically for its automotive industry and as part of the greater Port Elizabeth (Gqeberha) urban area.
-
D.
Tulbagh
Tulbagh is a historic town in South Africa’s Western Cape, known for its Cape Dutch architecture and surrounding wine-producing valley.
-
E.
Muizenberg
Muizenberg is a seaside suburb of Cape Town, South Africa, known for its popular surfing beach and colorful Victorian beach huts.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf06a3e208190a24e6cd9cb97e99c |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.