Triple
T34826988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrowmore Megalithic Cemetery |
E1003951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | megalithic cemetery |
C39792
|
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: megalithic cemetery Context triple: [Carrowmore Megalithic Cemetery, instanceOf, megalithic cemetery]
-
A.
megalithic site
chosen
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
-
B.
Bronze Age cemetery
A Bronze Age cemetery is an archaeological burial ground dating to the Bronze Age, typically containing graves, tombs, or barrows with associated artifacts that reflect the social structure, rituals, and material culture of the period.
-
C.
funerary site
A funerary site is a designated place where human or animal remains are buried, entombed, or otherwise ritually deposited, often accompanied by structures, markers, or artifacts related to death and commemoration.
-
D.
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.
-
E.
megalithic jar site
A megalithic jar site is an archaeological landscape characterized by the presence of large, carved stone jars, often arranged in groups, whose original function is typically associated with ancient ritual, funerary, or storage practices.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.