Triple
T11749729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeami Motokiyo |
E279373
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Yashima |
E519764
|
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: Yashima | Statement: [Zeami Motokiyo, notableWork, Yashima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yashima Context triple: [Zeami Motokiyo, notableWork, Yashima]
-
A.
Yashima
chosen
Yashima is a historic plateau and former island in Takamatsu, Kagawa Prefecture, known for its panoramic views of the Seto Inland Sea and as a key battlefield of the Genpei War.
-
B.
Himejima
Himejima is one of the small islands in Tokyo’s Mukojima Islands group, known for its remote, natural setting in the Pacific.
-
C.
Iōjima
Iōjima, more widely known as Iwo Jima, is a small volcanic island in the Pacific Ocean famous as the site of a major World War II battle between Japan and the United States.
-
D.
Tsukishima
Tsukishima is a man-made island and residential district in Tokyo’s Chūō ward, known for its high-rise apartments and famous monjayaki restaurants.
-
E.
Yoroshima
Yoroshima is a small island that is part of Japan’s subtropical Amami archipelago in Kagoshima Prefecture.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a508b0c4819082fbcc27d559ea2f |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e70dc788190850278a40a5a62e4 |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 8, 2026, 9:41 p.m.