Triple
T21366876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirakawa |
E526939
|
entity |
| Predicate | eraNameUsed |
P2938
|
FINISHED |
| Object | Jōryaku |
—
|
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: Jōryaku | Statement: [Shirakawa, eraNameUsed, Jōryaku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jōryaku Context triple: [Shirakawa, eraNameUsed, Jōryaku]
-
A.
Jōryaku
chosen
Jōryaku was a Japanese era of the late 11th century, notable as part of the Heian period’s imperial calendar system.
-
B.
Shōryaku
Shōryaku was a Japanese era name (nengō) of the late 10th century, used during the reign of Emperor Shirakawa.
-
C.
Jiryaku
Jiryaku was a Japanese era name (nengō) of the late Heian period, used during the reign of Emperor Go-Sanjō.
-
D.
Ryojun
Ryojun is the former Japanese name for Lüshunkou, a strategically important port city in northeastern China historically known for its military significance.
-
E.
Rokusei
Rokusei is a Japanese tokusatsu superhero team that succeeds Gosei in the narrative sequence of its series.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5bae5eb88190be6d9ff4dc03d52b |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 16, 2026, 5:09 p.m.