Triple
T23292901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Võ Văn Hoàn |
E590081
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Võ Văn |
—
|
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: Võ Văn | Statement: [Võ Văn Hoàn, givenName, Võ Văn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Võ Văn Context triple: [Võ Văn Hoàn, givenName, Võ Văn]
-
A.
Võ Văn Hoàn
chosen
Võ Văn Hoàn is a Vietnamese politician who has served as a vice chairman of the Ho Chi Minh City People's Committee.
-
B.
Võ Văn Hải
Võ Văn Hải is a Vietnamese individual notable enough to be recognized as a bearer of the Vietnamese surname Võ.
-
C.
Võ Chí Công
Võ Chí Công was a prominent Vietnamese revolutionary and politician who served as Chairman of the State Council (head of state) of Vietnam from 1987 to 1992.
-
D.
Võ Quốc Thắng
Võ Quốc Thắng is a Vietnamese businessman best known as a leading figure in the domestic football scene and as chairman of Đồng Tâm Long An Football Club.
-
E.
Cao Văn Viên
Cao Văn Viên was a South Vietnamese Army general who served as Chairman of the Joint General Staff and was one of the Republic of Vietnam’s most senior military leaders during the Vietnam War.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196ccd9b481909ab5d3504640025e |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:02 p.m.