Triple
T5905098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 皇居 |
E131323
|
entity |
| Predicate | 構成要素 |
P14960
|
FINISHED |
| Object |
伏見櫓
伏見櫓は、江戸城跡である東京の皇居内に現存する歴史的な三重櫓で、重要文化財にも指定されている城郭建築物である。
|
E554738
|
NE FINISHED |
How this triple was built (4 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: [皇居, 構成要素, 伏見櫓]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 伏見櫓 Context triple: [皇居, 構成要素, 伏見櫓]
-
A.
Fushimi Castle
Fushimi Castle is a historic Japanese castle in Kyoto associated with Toyotomi Hideyoshi and known for its role in the late Sengoku period and early Edo period.
-
B.
Osaka Castle
Osaka Castle is a historic Japanese fortress in Osaka, renowned for its grand architecture, surrounding park, and major role in Japan’s feudal history.
-
C.
Sakurada Gate
Sakurada Gate is a historic fortified entrance to the Tokyo Imperial Palace grounds, known for its role in Japan’s Edo-period defenses and as the site of notable historical events.
-
D.
Otemon Gate
Otemon Gate is a historic main entrance to the Tokyo Imperial Palace, notable for its traditional Japanese castle-style architecture and role in Japan’s imperial and feudal history.
-
E.
Suzakumon Gate
Suzakumon Gate is the grand southern main gate of the ancient Heijō Palace in Nara, Japan, historically serving as a ceremonial entrance to the imperial capital.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 伏見櫓 Triple: [皇居, 構成要素, 伏見櫓]
Generated description
伏見櫓は、江戸城跡である東京の皇居内に現存する歴史的な三重櫓で、重要文化財にも指定されている城郭建築物である。
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 伏見櫓 Target entity description: 伏見櫓は、江戸城跡である東京の皇居内に現存する歴史的な三重櫓で、重要文化財にも指定されている城郭建築物である。
-
A.
Fushimi Castle
Fushimi Castle is a historic Japanese castle in Kyoto associated with Toyotomi Hideyoshi and known for its role in the late Sengoku period and early Edo period.
-
B.
Osaka Castle
Osaka Castle is a historic Japanese fortress in Osaka, renowned for its grand architecture, surrounding park, and major role in Japan’s feudal history.
-
C.
Sakurada Gate
Sakurada Gate is a historic fortified entrance to the Tokyo Imperial Palace grounds, known for its role in Japan’s Edo-period defenses and as the site of notable historical events.
-
D.
Otemon Gate
Otemon Gate is a historic main entrance to the Tokyo Imperial Palace, notable for its traditional Japanese castle-style architecture and role in Japan’s imperial and feudal history.
-
E.
Suzakumon Gate
Suzakumon Gate is the grand southern main gate of the ancient Heijō Palace in Nara, Japan, historically serving as a ceremonial entrance to the imperial capital.
- F. None of above. chosen
Provenance (5 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c049fdb3e08190a72337ab4f48bc8e |
completed | March 22, 2026, 7:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b16ba6c881908e9a909bf86ea92d |
completed | March 23, 2026, 3:20 a.m. |
| NEDg | Description generation | batch_69c0b27438a08190ab6b72c8fd682bf6 |
completed | March 23, 2026, 3:24 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c0b309a70081908ad3e819879b17e4 |
completed | March 23, 2026, 3:27 a.m. |
Created at: March 22, 2026, 3:59 p.m.