Triple
T16178428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoji Sadao |
E392625
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Shoji |
E905112
|
NE 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: Shoji | Statement: [Shoji Sadao, givenName, Shoji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shoji Context triple: [Shoji Sadao, givenName, Shoji]
-
A.
Shōji
chosen
Shōji is a Japanese masculine given name that can be written with various kanji and is borne by numerous notable figures in fields such as the military, arts, and sports.
-
B.
Shōji-ko
Shōji-ko is one of the Fuji Five Lakes in Yamanashi Prefecture, Japan, known for its scenic views of Mount Fuji and relatively undeveloped, tranquil surroundings.
-
C.
Shimabukuro
Shimabukuro is a Japanese surname most notably associated with virtuoso ukulele player Jake Shimabukuro.
-
D.
Ogori Shoji
Ogori Shoji was the original Japanese apparel company that later evolved into and was renamed Fast Retailing, the parent firm of Uniqlo.
-
E.
Yokoze
Yokoze is a small town in Saitama Prefecture, Japan, known for its rural scenery and proximity to the Chichibu mountain area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205ab3108190a84fc2dfe61d5044 |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fffefe4dc08190a6cc43a448ae6554 |
completed | May 10, 2026, 3:43 a.m. |
Created at: April 10, 2026, 5:02 a.m.