Triple
T27970767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francesco church and museum complex |
E706347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church and museum complex |
C41479
|
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: church and museum complex Context triple: [San Francesco church and museum complex, instanceOf, church and museum complex]
-
A.
Christian church complex
A Christian church complex is an integrated group of religious buildings and spaces, typically including a main church, auxiliary chapels, administrative and community facilities, and associated outdoor areas, dedicated to Christian worship, ministry, and communal life.
-
B.
ecclesiastical museum
chosen
An ecclesiastical museum is a specialized institution that collects, preserves, and exhibits religious artifacts, artworks, and liturgical objects related to the history and practice of a particular church or faith tradition.
-
C.
museum building complex
A museum building complex is a coordinated group of structures and spaces designed to collect, preserve, exhibit, and interpret cultural, historical, artistic, or scientific artifacts for public education and enjoyment.
-
D.
landmark church
A landmark church is a historically or architecturally significant Christian place of worship that serves as a prominent visual and cultural reference point within its surrounding area.
-
E.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:37 p.m.