Triple
T6007366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volta Region |
E133744
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Ho |
E406972
|
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: Ho | Statement: [Volta Region, capital, Ho]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ho Context triple: [Volta Region, capital, Ho]
-
A.
Ho
Ho are an indigenous Adivasi community of eastern India, primarily inhabiting parts of Jharkhand and Odisha, known for their Austroasiatic Ho language and distinct cultural traditions.
-
B.
Ho
Ho is the given name of the Korean-born contemporary artist Do Ho Suh, known for his large-scale installations exploring space, memory, and identity.
-
C.
Ho
"Ho" is a track featured on Ludacris's debut studio album "Back for the First Time."
-
D.
Ho
chosen
Ho is a town in southeastern Ghana that serves as the capital of the Volta Region and an important administrative and commercial center.
-
E.
Ho
Ho is a common East Asian surname used in various cultures, including Chinese and Korean, often representing different characters and lineages depending on the language and region.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f13d9908190a11d9bef8652db93 |
completed | March 22, 2026, 8:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c10895559081908b9efdd32ecef37f |
completed | March 23, 2026, 9:32 a.m. |
Created at: March 22, 2026, 4:06 p.m.