Triple
T28467095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tran Thien Khiem |
E720320
|
entity |
| Predicate | hasNameInVietnameseOrder |
P154571
|
FINISHED |
| Object | Tran Thien Khiem |
—
|
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: Tran Thien Khiem | Statement: [Tran Thien Khiem, hasNameInVietnameseOrder, Tran Thien Khiem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInVietnameseOrder Context triple: [Tran Thien Khiem, hasNameInVietnameseOrder, Tran Thien Khiem]
-
A.
nameOrderInVietnamese
chosen
Indicates the conventional ordering of a person's name components when written or spoken in Vietnamese.
-
B.
nameInVietnamese
Indicates that one entity is the Vietnamese-language name or designation of another entity.
-
C.
hasNameInLao
Indicates that an entity has a specific name expressed in the Lao language.
-
D.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
E.
nameOrderInChinese
Indicates that the entities are arranged in the order that personal names are written or spoken in Chinese (family name first, given name second).
- F. None of above.
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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 2:45 a.m.