Triple
T12285364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rongorongo tablets |
E292815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage objects |
C9575
|
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: cultural heritage objects Context triple: [Rongorongo tablets, instanceOf, cultural heritage objects]
-
A.
cultural heritage object collection
A cultural heritage object collection is an organized assemblage of artifacts, artworks, or historical items preserved and managed to represent and transmit the cultural, historical, or artistic legacy of a community or society.
-
B.
cultural heritage
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
-
C.
historical artifacts
chosen
Historical artifacts are physical objects created or used by people in the past that provide tangible evidence and insight into historical events, cultures, and ways of life.
-
D.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
E.
cultural heritage element
A cultural heritage element is a tangible or intangible manifestation of a community’s traditions, practices, expressions, knowledge, or artifacts that is valued, preserved, and transmitted across generations.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.