Triple
T18289896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirakawa-tennō |
E438082
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Chōshō |
—
|
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: Chōshō | Statement: [Shirakawa-tennō, eraName, Chōshō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chōshō Context triple: [Shirakawa-tennō, eraName, Chōshō]
-
A.
Chōshō
chosen
Chōshō was a Japanese era (nengō) of the early 12th century, falling within the reign of Emperor Toba.
-
B.
Chōhō
Chōhō was a Japanese era name (nengō) of the Heian period, notable for marking part of Emperor Ichijō’s reign around the turn of the 11th century.
-
C.
Chō
Chō is a Japanese surname borne by various notable individuals across fields such as the military, arts, and entertainment.
-
D.
Chōryaku
Chōryaku was a Japanese era name (nengō) used during the Heian period, marking a specific span of years in the imperial calendar.
-
E.
Shinshiro
Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
- 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.