Triple
T16158610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedensreich Hundertwasser |
E392115
|
entity |
| Predicate | burialDetail |
P121622
|
FINISHED |
| Object | buried under a tulip tree |
—
|
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: buried under a tulip tree | Statement: [Friedensreich Hundertwasser, burialDetail, buried under a tulip tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialDetail Context triple: [Friedensreich Hundertwasser, burialDetail, buried under a tulip tree]
-
A.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
-
D.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
E.
periodOfBurial
Indicates the time period or date range during which the burial of an entity took place.
- F. None of above. chosen
Provenance (4 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5c9cd0819090e34ee163ffb118 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e18445155481909892b8aaa23cc159 |
completed | April 17, 2026, 12:52 a.m. |
Created at: April 10, 2026, 5:01 a.m.