Triple
T18289888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirakawa-tennō |
E438082
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Hōan |
—
|
NE NERFINISHED |
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ōan | Statement: [Shirakawa-tennō, eraName, Hōan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hōan Context triple: [Shirakawa-tennō, eraName, Hōan]
-
A.
Hōan
chosen
Hōan was a Japanese era name (nengō) of the early 12th century, used during the reign of Emperor Toba.
-
B.
Hōshō
Hōshō was the Imperial Japanese Navy’s pioneering aircraft carrier and the world’s first purpose-built carrier to enter service.
-
C.
Hōen
Hōen was a Japanese era name (nengō) of the late Heian period, used during the reign of Emperor Toba.
-
D.
Hōki
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.
-
E.
Hoan-ya
Hoan-ya is an alternative name for the Hoanya language, an indigenous Formosan language historically spoken in Taiwan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fd65888190afdbb29dc60066af |
completed | April 19, 2026, 4:21 p.m. |
Created at: April 10, 2026, 10:35 a.m.