Triple
T22440475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 乾門 |
E554740
|
entity |
| Predicate | 関連施設 |
P81092
|
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: [乾門, 関連施設, 桜田門]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 桜田門 Context triple: [乾門, 関連施設, 桜田門]
-
A.
Sakurada Gate
chosen
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.
-
B.
Ishikawa Gate
Ishikawa Gate is a historic fortified entrance to Kanazawa Castle in Kanazawa, Japan, known for its traditional wooden architecture and role as a symbol of the former castle town.
-
C.
半蔵門
半蔵門は、東京都千代田区に位置する皇居の西側に設けられた門で、江戸城時代からの歴史を持つ重要な出入口です。
-
D.
神宮前
神宮前 is a district in Shibuya, Tokyo, known for its proximity to Meiji Shrine and the fashionable Harajuku and Omotesando areas.
-
E.
Hirakawamon Gate
Hirakawamon Gate is a historic fortified entrance of the former Edo Castle in Tokyo, now part of the Imperial Palace grounds and noted for its traditional Japanese castle architecture.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
Created at: April 16, 2026, 8:47 p.m.