Triple
T17132774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonnanaro culture |
E415761
|
entity |
| Predicate | usesBurialCustom |
P74935
|
FINISHED |
| Object | rock-cut tombs |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: rock-cut tombs | Statement: [Bonnanaro culture, usesBurialCustom, rock-cut tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBurialCustom Context triple: [Bonnanaro culture, usesBurialCustom, rock-cut tombs]
-
A.
hasBurialCustoms
chosen
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
B.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
E.
possiblyBurialOf
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
- F. None of above.
Provenance (3 batches)
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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02ba4cc8190b6f433e08e958d83 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.