Triple
T23366261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Võ Văn Hải |
E593330
|
entity |
| Predicate | nameInNativeLanguage |
P1435
|
FINISHED |
| Object | "Võ Văn Hải" (Vietnamese) |
—
|
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 Hải" (Vietnamese) | Statement: [Võ Văn Hải, nameInNativeLanguage, "Võ Văn Hải" (Vietnamese)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: "Võ Văn Hải" (Vietnamese) Context triple: [Võ Văn Hải, nameInNativeLanguage, "Võ Văn Hải" (Vietnamese)]
-
A.
Võ (Vietnamese surname)
Võ is a common Vietnamese family name, often associated with historical military leaders and widely romanized as "Vo" in English-speaking contexts.
-
B.
Võ Văn Hải
chosen
Võ Văn Hải is a Vietnamese individual notable enough to be recognized as a bearer of the Vietnamese surname Võ.
-
C.
Võ
Võ is a common Vietnamese surname shared by many notable figures in politics, military history, arts, and sports.
-
D.
Võ Văn Hoàn
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.
-
E.
Võ Huy Toàn
Võ Huy Toàn is a Vietnamese professional footballer known for playing as a winger and representing Vietnam at the international level.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ac7494819082e98ac5632eba28 |
completed | April 29, 2026, 6:09 a.m. |
Created at: April 17, 2026, 5:31 p.m.