Triple
T36876127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomba Ildebranda |
E911347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Etruscan tomb |
C1065
|
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: Etruscan tomb Context triple: [Tomba Ildebranda, instanceOf, Etruscan tomb]
-
A.
Nabataean tomb
A Nabataean tomb is a rock-cut or freestanding funerary monument, typically carved into sandstone cliffs and characterized by a blend of local, Hellenistic, and Near Eastern architectural elements, used by the Nabataean civilization to bury and honor their dead.
-
B.
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.
-
C.
Etruscan architectural structure
An Etruscan architectural structure is a building or monument characterized by the use of mudbrick and timber construction on stone foundations, deep columned porches, and rich terracotta decoration, reflecting the religious, social, and artistic practices of the Etruscan civilization.
-
D.
tomb
chosen
A tomb is a structure or chamber, often built of stone or underground, designed to house and commemorate the dead and their remains.
-
E.
Etruscan wall paintings
Etruscan wall paintings are vibrant frescoes adorning tomb and temple interiors, depicting lively banquets, dances, mythological scenes, and daily life that reflect the social, religious, and aesthetic values of ancient Etruscan society.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.