Triple
T1454430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thuy |
E31365
|
entity |
| Predicate | nameOrderInCulture |
P1082
|
FINISHED |
| Object | follows family name in Vietnamese naming order |
—
|
LITERAL 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: follows family name in Vietnamese naming order | Statement: [Thuy, nameOrderInCulture, follows family name in Vietnamese naming order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameOrderInCulture Context triple: [Thuy, nameOrderInCulture, follows family name in Vietnamese naming order]
-
A.
nameOrderInJapan
Indicates that the person’s name is written or presented in the Japanese order, with the family name appearing before the given name.
-
B.
positionOnCulture
Indicates the stance, viewpoint, or opinion that one entity holds regarding cultural issues, practices, or phenomena in relation to another entity or context.
-
C.
nameInLatinAlphabet
Indicates that an entity’s name is written or represented using the Latin alphabet.
-
D.
languageFamilyPosition
Indicates the hierarchical position or role that a language occupies within its broader language family structure.
-
E.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57fead881909a47188ce7312406 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.