Triple
T31609088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Hansen Tammsaare (symbolic grave) |
E806575
|
entity |
| Predicate | hasNotableBurialType |
P6490
|
FINISHED |
| Object | symbolic burial |
—
|
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: symbolic burial | Statement: [Anton Hansen Tammsaare (symbolic grave), hasNotableBurialType, symbolic burial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBurialType Context triple: [Anton Hansen Tammsaare (symbolic grave), hasNotableBurialType, symbolic burial]
-
A.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
B.
hasTypeOfBurial
chosen
Indicates the specific kind or method of burial associated with an entity.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
E.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: April 30, 2026, 10:36 p.m.