Triple
T37099296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okamura Akemi |
E918653
|
entity |
| Predicate | hasJapaneseNameOrder |
P20511
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Okamura Akemi, hasJapaneseNameOrder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJapaneseNameOrder Context triple: [Okamura Akemi, hasJapaneseNameOrder, true]
-
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.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
C.
hasJapaneseSurname
Indicates that the person or entity possesses a surname that is of Japanese origin or is commonly used in Japanese naming conventions.
-
D.
romanizedOrder
Indicates that the entities are arranged or compared according to the order of their romanized (Latin-script) representations.
-
E.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.