Triple
T23292513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chūmon (Middle Gate) |
E590069
|
entity |
| Predicate | hasNameInJapanese |
P28734
|
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: [Chūmon (Middle Gate), hasNameInJapanese, 中門]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 中門 Context triple: [Chūmon (Middle Gate), hasNameInJapanese, 中門]
-
A.
中門
chosen
中門 is the central gate of Hōryū-ji Temple in Nara, Japan, renowned as part of one of the world’s oldest surviving wooden Buddhist temple complexes.
-
B.
弘化門
弘化門 is a historic gate of Gyeongbokgung Palace in Seoul, South Korea, serving as one of its main entrances during the Joseon Dynasty.
-
C.
平川門
平川門は、東京都千代田区にある皇居の北側に位置する主要な門の一つで、江戸城時代から続く歴史的な城門です。
-
D.
大手門
大手門は、かつて江戸城の正門として機能し、現在は皇居東御苑の主要な出入口となっている歴史的な城門です。
-
E.
田安門
田安門は、東京都千代田区の皇居東側に位置する江戸城の門の一つで、重要文化財にも指定されている歴史的建造物である。
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cc20c08190a6a678befe1061dd |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:02 p.m.