Triple
T29352794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of Archaeology and Anthropology, University of Cambridge |
E744358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | museum in Cambridge |
C15870
|
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: museum in Cambridge Context triple: [Museum of Archaeology and Anthropology, University of Cambridge, instanceOf, museum in Cambridge]
-
A.
museum in England
chosen
A museum in England is a public or private institution that collects, preserves, researches, and exhibits objects of historical, artistic, scientific, or cultural significance, primarily related to English or broader global heritage, for education and public enjoyment.
-
B.
castle museum
A castle museum is a historic fortress or palace preserved and curated to exhibit artifacts, architecture, and stories related to its past and cultural heritage.
-
C.
church museum
A church museum is a cultural institution housed in or associated with a church that preserves, exhibits, and interprets religious artifacts, art, and historical objects related to the church’s heritage and faith traditions.
-
D.
museum in Denmark
A museum in Denmark is a cultural institution that collects, preserves, researches, and exhibits artworks, artifacts, or historical objects relevant to Danish or global heritage for public education and enjoyment.
-
E.
museum in Connecticut
A museum in Connecticut is a cultural institution within the state that collects, preserves, and exhibits art, artifacts, or historical materials for public education and enrichment.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:07 p.m.