Triple
T16859539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ichijō |
E409871
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Shōryaku |
—
|
NE ONNED1 |
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: Shōryaku | Statement: [Emperor Ichijō, eraName, Shōryaku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shōryaku Context triple: [Emperor Ichijō, eraName, Shōryaku]
-
A.
Shōryaku
chosen
Shōryaku was a Japanese era name (nengō) of the late 10th century, used during the reign of Emperor Shirakawa.
-
B.
Ryojun
Ryojun is the former Japanese name for Lüshunkou, a strategically important port city in northeastern China historically known for its military significance.
-
C.
Shimotsuki
Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
-
D.
Katsuragi
Katsuragi was a late-war Imperial Japanese Navy aircraft carrier that served in the Pacific Theater during World War II.
-
E.
Katsuragi
Katsuragi is a city in Japan known for its location in Nara Prefecture and its historical and cultural ties to the ancient Yamato region.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b501f72881909f7600311705fb33 |
completed | April 18, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01954069e0819087fab0a782a83f39 |
finalizing | May 11, 2026, 8:37 a.m. |
Created at: April 10, 2026, 5:24 a.m.