Triple
T11270377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoku Nihongi |
E266794
|
entity |
| Predicate | relatedWork |
P37
|
FINISHED |
| Object | Nihon Kōki |
E915178
|
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: Nihon Kōki | Statement: [Shoku Nihongi, relatedWork, Nihon Kōki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nihon Kōki Context triple: [Shoku Nihongi, relatedWork, Nihon Kōki]
-
A.
Nihon Kōki
chosen
Nihon Kōki is an early Heian-period Japanese historical chronicle and one of the Six National Histories, covering events following those recorded in the Shoku Nihongi.
-
B.
Sanyo-Onoda
Sanyo-Onoda is a coastal industrial city in western Japan known for its cement and chemical industries and its location along the Seto Inland Sea.
-
C.
Nihon Sekkei
Nihon Sekkei is a major Japanese architectural and urban design firm known for large-scale commercial and mixed-use developments.
-
D.
Nihon Goraku Bussan
Nihon Goraku Bussan was the original Japanese company that evolved into Sega, a major video game and entertainment corporation.
-
E.
Shibaura Futo
Shibaura Futo is a waterfront district and pier area in Tokyo’s Minato Ward, known for its views of Tokyo Bay and proximity to the Rainbow Bridge.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9506204819089dc0827483bd948 |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f4229c7081909da6b22ee6bf4905 |
completed | April 19, 2026, 3:26 p.m. |
Created at: April 8, 2026, 9:31 p.m.