Triple
T11549671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rōmon gate |
E273857
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | 楼門 |
E815748
|
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: 楼門 | Statement: [Rōmon gate, hasAlternativeName, 楼門]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 楼門 Context triple: [Rōmon gate, hasAlternativeName, 楼門]
-
A.
赤門
赤門（Akamon, the Red Gate）is a historic vermilion-painted gate in Tokyo, best known as a symbol of the University of Tokyo and an Important Cultural Property of Japan.
-
B.
平川門
平川門は、東京都千代田区にある皇居の北側に位置する主要な門の一つで、江戸城時代から続く歴史的な城門です。
-
C.
城门楼
chosen
城门楼是一种建于城门之上的多层楼阁式建筑，兼具防御、瞭望与礼仪象征等功能，在中国古代城池与宫城中极具代表性。
-
D.
端门
端门是位于北京中轴线上、介于天安门与太庙、社稷坛之间的明清皇城城门之一，曾是皇帝出入宫城的重要门户。
-
E.
Đoan Môn Gate
Đoan Môn Gate is the main southern entrance and ceremonial gateway to the Imperial Citadel of Thăng Long in Hanoi, Vietnam, reflecting the citadel’s historic royal architecture.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e685e7e6488190a3704e2028df5add |
completed | April 20, 2026, 8 p.m. |
Created at: April 8, 2026, 9:37 p.m.