Triple
T27125283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isonokami Kofun cluster |
E687109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | burial mound group |
C51282
|
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: burial mound group Context triple: [Isonokami Kofun cluster, instanceOf, burial mound group]
-
A.
archaeological mound
An archaeological mound is an artificial or modified natural elevation of earth, stone, or debris created by past human activity, often containing buried cultural materials and serving as a key source of information about ancient societies.
-
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.
Anglo-Saxon burial mound
An Anglo-Saxon burial mound is an earthen or stone-built barrow constructed in early medieval England to cover and mark the grave of an individual, often accompanied by grave goods and sometimes elaborate funerary structures.
-
D.
funerary site
chosen
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.
-
E.
megalithic site
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 9:01 a.m.