Triple
T26134310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metropolitan Foundation for History and Culture |
E659334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public cultural organization |
C84
|
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: public cultural organization Context triple: [Tokyo Metropolitan Foundation for History and Culture, instanceOf, public cultural organization]
-
A.
cultural institution
chosen
A cultural institution is an organized establishment, such as a museum, library, theater, or gallery, dedicated to preserving, interpreting, and promoting the arts, heritage, and shared cultural expressions of a community or society.
-
B.
cultural office
A cultural office is an organizational unit or agency dedicated to promoting, managing, and supporting cultural activities, policies, and initiatives within a community, institution, or region.
-
C.
international cultural organization
An international cultural organization is an entity that operates across national borders to promote, preserve, and facilitate the exchange of arts, heritage, and cultural practices among diverse societies.
-
D.
socio-cultural organization
A socio-cultural organization is a structured group formed to promote, preserve, and develop shared social values, cultural practices, and community interests within a specific population or across diverse communities.
-
E.
arts organisation
An arts organisation is an entity that supports, produces, presents, or promotes artistic and cultural activities, often serving as a hub connecting artists, audiences, and communities.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:16 p.m.