Triple
T22440395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伏見櫓 |
E554738
|
entity |
| Predicate | 別名 |
P39
|
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.
伏見櫓
chosen
伏見櫓は、江戸城跡である東京の皇居内に現存する歴史的な三重櫓で、重要文化財にも指定されている城郭建築物である。
-
B.
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.
-
C.
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.
-
D.
Akashi Castle
Akashi Castle is a historic Japanese hilltop fortress in Hyōgo Prefecture, known for its surviving turrets and scenic views over the city and nearby coastline.
-
E.
Iga Ueno Castle
Iga Ueno Castle is a historic Japanese hilltop fortress in Iga, Mie Prefecture, renowned for its impressive stone walls and association with ninja heritage.
- 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.