Triple
T13284606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joko |
E316410
|
entity |
| Predicate | romanizes |
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: [Joko, romanizes, Jōkō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jōkō Context triple: [Joko, romanizes, 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.
Kujō
Kujō is a Japanese surname historically associated with an aristocratic kuge family that was part of the influential Fujiwara clan.
-
C.
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.
-
D.
Fumimaro
Fumimaro was a Japanese nobleman and politician who served multiple terms as Prime Minister of Japan in the years leading up to and during the early stages of World War II.
-
E.
Kiyosu
Kiyosu is a city in central Japan known historically for Kiyosu Castle and its role as a political center during the Sengoku period.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99047531c819087aa6406de1ddc82 |
completed | April 11, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a5a98488190804a97a052741377 |
completed | May 3, 2026, 8:42 a.m. |
Created at: April 9, 2026, 9:27 p.m.