Triple
T16442949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten'ō |
E399349
|
entity |
| Predicate | follows |
P134
|
FINISHED |
| Object | Hōki |
E1204860
|
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: Hōki | Statement: [Ten'ō, follows, Hōki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hōki Context triple: [Ten'ō, follows, Hōki]
-
A.
Hōki
chosen
Hōki was a Japanese era of the Nara period, marked by the reign of Emperor Kōnin and known for continued consolidation of imperial authority and Buddhist culture.
-
B.
Hōan
Hōan was a Japanese era name (nengō) of the early 12th century, used during the reign of Emperor Toba.
-
C.
Gyōkyō
Gyōkyō was a Buddhist monk traditionally credited with establishing the important Shinto-Buddhist shrine Iwashimizu Hachimangū in Japan.
-
D.
Hokuzan
Hokuzan was a medieval kingdom in northern Okinawa that existed before the unification of the Ryukyu Islands under the Ryukyu Kingdom.
-
E.
Hozomon
Hozomon is the grand inner gate of Senso-ji Temple in Asakusa, Tokyo, known for its massive red lanterns and imposing traditional architecture.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd8d2988190acb5722a15623319 |
completed | April 18, 2026, 7:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f4b738881908f8a205466397f33 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:10 a.m.