Triple
T2984113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jōkō |
E80579
|
entity |
| Predicate | hasRomanization |
P2508
|
FINISHED |
| Object | Jōkō |
E80579
|
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: Jōkō | Statement: [Jōkō, hasRomanization, Jōkō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jōkō Context triple: [Jōkō, hasRomanization, Jōkō]
-
A.
Jōkō
chosen
Jōkō is the Japanese honorific title traditionally given to a retired emperor who has abdicated the throne.
-
B.
Tennō
Tennō is the Japanese term for the Emperor of Japan, regarded as the ceremonial and symbolic monarch and, in tradition, a descendant of the sun goddess Amaterasu.
-
C.
Kishi
Kishi is a Japanese surname borne by various notable figures in politics, arts, and entertainment.
-
D.
Shinzo
Shinzo is the given name of Shinzo Abe, the former Prime Minister of Japan and a prominent modern Japanese political leader.
-
E.
Shōhō
Shōhō was a Japanese light aircraft carrier of the Imperial Japanese Navy during World War II, notable for being the first Japanese carrier sunk in the war during the Battle of the Coral Sea.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c481fc81909971c96352a881b4 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1de999ff88190824ecdc164496d37 |
completed | March 11, 2026, 9:28 p.m. |
Created at: March 8, 2026, 2:59 p.m.