Triple
T33525195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musashi Kokubunji temple ruins |
E858618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic site in Japan |
C11600
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic site in Japan Context triple: [Musashi Kokubunji temple ruins, instanceOf, historic site in Japan]
-
A.
ancient Japanese city
An ancient Japanese city is a historical urban center in Japan characterized by traditional wooden architecture, temples and shrines, and a layout reflecting the political, cultural, and religious life of its era.
-
B.
Historic site in South Korea
A historic site in South Korea is a culturally or historically significant location, such as ancient palaces, temples, fortresses, or traditional villages, officially recognized for its heritage value and preserved for public education and tourism.
-
C.
Historic Site of South Korea
A Historic Site of South Korea is a designated location recognized by the government for its significant historical, cultural, or academic value, often associated with important events, figures, or periods in Korean history.
-
D.
medieval Japanese town ruin
A medieval Japanese town ruin is the archaeological remains of a historical urban settlement in Japan, preserving traces of its streets, buildings, defenses, and daily life from the Middle Ages.
-
E.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
- F. None of above.
Provenance (1 batch)
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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.