Triple
T1454301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê |
E31362
|
entity |
| Predicate | nameOrder |
P20511
|
FINISHED |
| Object | family name appears first in Vietnamese full name |
—
|
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: family name appears first in Vietnamese full name | Statement: [Lê, nameOrder, family name appears first in Vietnamese full name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameOrder Context triple: [Lê, nameOrder, family name appears first in Vietnamese full name]
-
A.
nameOrderInJapan
chosen
Indicates that the person’s name is written or presented in the Japanese order, with the family name appearing before the given name.
-
B.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
C.
namesAs
Indicates that one entity assigns or uses a particular name or label to refer to another entity.
-
D.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
- 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.