Triple
T13914733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 交泰殿 |
E334590
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | 内廷 |
E340932
|
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: [交泰殿, partOf, 内廷]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 内廷 Context triple: [交泰殿, partOf, 内廷]
-
A.
皇居
皇居は、日本の天皇と皇室の公的な居所および宮中行事の中心となる東京都千代田区に位置する宮殿・庭園の総称である。
-
B.
Quốc Tử Giám
Quốc Tử Giám is Vietnam’s historic imperial academy in Hanoi, regarded as the country’s first national university and a major Confucian educational and cultural site.
-
C.
長和殿
長和殿は、日本の皇居内に位置し、公式行事や儀式などに用いられる主要な宮殿建物の一つである。
-
D.
交泰殿
交泰殿 is a historic hall within Beijing’s Forbidden City, traditionally used for important imperial ceremonies and symbolizing the harmony of heaven and earth in Chinese imperial architecture.
-
E.
Inner Court of the Forbidden City
chosen
The Inner Court of the Forbidden City was the residential and political center of the Chinese emperors, housing their private palaces and serving as the core of imperial life during the Ming and Qing dynasties.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c72a345481908f8552bca7bb1a5a |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:16 p.m.