Triple
T6240766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōkuninushi |
E139592
|
entity |
| Predicate | domain |
P87
|
FINISHED |
| Object | land of Izumo |
E78244
|
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: land of Izumo | Statement: [Ōkuninushi, domain, land of Izumo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: land of Izumo Context triple: [Ōkuninushi, domain, land of Izumo]
-
A.
Tenri
Tenri is a small city in Japan known as the headquarters of the Tenrikyo religion and for its rich archaeological and cultural heritage.
-
B.
Kumano
Kumano was a Mogami-class heavy cruiser of the Imperial Japanese Navy that served during World War II.
-
C.
Kumano
Kumano is a coastal city in Japan’s Mie Prefecture known for its scenic Kumano Kodo pilgrimage routes and rugged natural landscapes.
-
D.
Izumo
chosen
Izumo is a coastal city in Japan’s Shimane Prefecture, best known for the ancient Shinto shrine Izumo Taisha, one of the country’s most important religious sites.
-
E.
Kaga no Kuni
Kaga no Kuni was a historical province of Japan located in what is now southern Ishikawa Prefecture on the island of Honshu.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063067d9c819085a18d9d03939266 |
completed | March 22, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20e07bff8819091ca881c9b4daaf6 |
completed | March 24, 2026, 4:07 a.m. |
Created at: March 22, 2026, 4:23 p.m.