Triple
T22139739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陸奥国 |
E547124
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 陸奥国 |
—
|
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: 陸奥国 | Statement: [陸奥国, nativeName, 陸奥国]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 陸奥国 Context triple: [陸奥国, nativeName, 陸奥国]
-
A.
陸奥国
chosen
陸奥国 was an expansive historical province in northeastern Honshū, Japan, encompassing much of the modern Tōhoku region.
-
B.
両国
両国 is a district in Tokyo, Japan, best known for its sumo culture and the Ryōgoku Kokugikan sumo stadium.
-
C.
Jochid ulus
Jochid ulus was the Mongol state in the western part of the empire that evolved into the Golden Horde under the descendants of Jochi.
-
D.
Reihoku
Reihoku is a coastal town located on the Amakusa Islands in Kumamoto Prefecture, Japan, known for its fishing industry and scenic seaside landscapes.
-
E.
Kingdom of Hoshido
The Kingdom of Hoshido is a peaceful, Eastern-inspired nation in the Fire Emblem Fates video game, known for its strong sense of honor, familial bonds, and conflict with the neighboring Kingdom of Nohr.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bda1208190b851ae5c68b760e9 |
completed | April 28, 2026, 9:42 p.m. |
Created at: April 16, 2026, 8:32 p.m.