Triple
T23271001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambo |
E588288
|
entity |
| Predicate | alternateName |
P39
|
FINISHED |
| Object | Ovambo |
—
|
NE NERFINISHED |
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: Ovambo | Statement: [Ambo, alternateName, Ovambo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ovambo Context triple: [Ambo, alternateName, Ovambo]
-
A.
Ovambo
chosen
Ovambo is a Bantu language spoken primarily by the Ovambo people in northern Namibia and southern Angola.
-
B.
Ohangwena
Ohangwena is a settlement in northern Namibia that lends its name to the surrounding Ohangwena Region.
-
C.
Assosa
Assosa is a town in western Ethiopia that serves as the administrative and economic center of the Benishangul-Gumuz Region near the Sudanese border.
-
D.
Shoshong
Shoshong is a historic village in Botswana known for its role as a 19th-century trade and missionary center and former capital of the Bamangwato people.
-
E.
Omaruru
Omaruru is a small historic town in central Namibia known for its colonial-era architecture, vineyards, and role as a local trading and farming center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957418fc819085ee528622e0c6de |
completed | April 29, 2026, 5:21 a.m. |
Created at: April 17, 2026, 4:45 p.m.