Triple
T6536195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izanagi |
E152368
|
entity |
| Predicate | fledFrom |
P11257
|
FINISHED |
| Object | Yomi |
E605685
|
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: Yomi | Statement: [Izanagi, fledFrom, Yomi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yomi Context triple: [Izanagi, fledFrom, Yomi]
-
A.
Yomi
chosen
Yomi is the shadowy land of the dead in Japanese mythology, often depicted as a gloomy underworld where the deceased reside.
-
B.
Tezu
Tezu is a prominent town in northeastern India known as an important administrative and cultural center in the Lohit district of Arunachal Pradesh.
-
C.
Teimei
Teimei is the posthumous name of the Japanese empress consort of Emperor Taishō, who served as Empress of Japan in the early 20th century.
-
D.
Keiyo
Keiyo is a Southern Nilotic language spoken primarily by the Keiyo people of Kenya’s Rift Valley region.
-
E.
Sachinomiya
Sachinomiya was the childhood name of Emperor Meiji, the Japanese monarch who oversaw the country's rapid modernization and the Meiji Restoration.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc238688190aca143b22b8a399c |
completed | March 27, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6e41b0a8881908aebef421a6d403c |
completed | March 27, 2026, 8:10 p.m. |
Created at: March 27, 2026, 1:46 p.m.