Triple
T14457924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shendao |
E358503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | funerary architecture feature |
C29722
|
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: funerary architecture feature Context triple: [Shendao, instanceOf, funerary architecture feature]
-
A.
cemetery architectural feature
chosen
A cemetery architectural feature is a designed structural or ornamental element within a burial ground—such as gates, mausoleums, monuments, pathways, or chapels—that shapes its spatial organization, symbolism, and visitor experience.
-
B.
Funerary structure
A funerary structure is a built form or monument specifically designed to house, mark, or commemorate the dead and associated burial practices.
-
C.
burial monument
A burial monument is a constructed marker or structure, such as a tomb, gravestone, or mausoleum, that commemorates and identifies the resting place of the dead.
-
D.
mausoleum
A mausoleum is a free-standing, often monumental building constructed as a tomb to house and honor the dead.
-
E.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.