Triple
T11161040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamiyama |
E264034
|
entity |
| Predicate | hasNameOrderInWesternContexts |
P28784
|
FINISHED |
| Object | surnameLast |
—
|
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: surnameLast | Statement: [Kamiyama, hasNameOrderInWesternContexts, surnameLast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameOrderInWesternContexts Context triple: [Kamiyama, hasNameOrderInWesternContexts, surnameLast]
-
A.
hasNameOrder
chosen
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
B.
nameOrderInJapan
Indicates that the person’s name is written or presented in the Japanese order, with the family name appearing before the given name.
-
C.
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).
-
D.
nameFormInLatin
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
-
E.
isEquivalentSurnameInEnglish
Indicates that two surnames are considered equivalent when rendered or transliterated into English.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8817a90819087820d5241c58851 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.