Triple
T15498518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 52: Taisanji |
E378886
|
entity |
| Predicate | hasMainHall |
P6080
|
FINISHED |
| Object | Hondō |
E1150924
|
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: Hondō | Statement: [Temple 52: Taisanji, hasMainHall, Hondō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hondō Context triple: [Temple 52: Taisanji, hasMainHall, Hondō]
-
A.
Hondō
chosen
Hondō is the main worship hall of a Japanese Buddhist temple, typically housing its principal sacred image.
-
B.
Takarano
Takarano is a small settlement on the atoll of Tabiteuea in the island nation of Kiribati, located in the central Pacific Ocean.
-
C.
Takarano
Takarano is a village located on the atoll of Abaiang in the island nation of Kiribati.
-
D.
Higashiura
Higashiura is a town in central Japan located within Aichi Prefecture, known as a residential community in the Chita Peninsula area.
-
E.
Nagahori
Nagahori is a district in Osaka, Japan, known primarily as an urban area served by the Osaka Metro Nagahori Tsurumi-ryokuchi Line.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fb0aee081909db1c54349ec8492 |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf0a12e081908d7d2ae7c9774f94 |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 3:53 a.m.