Triple
T30624204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Death |
E779527
|
entity |
| Predicate | culturallyRole |
P3795
|
FINISHED |
| Object | explains what happens after death |
—
|
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: explains what happens after death | Statement: [Lord of Death, culturallyRole, explains what happens after death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturallyRole Context triple: [Lord of Death, culturallyRole, explains what happens after death]
-
A.
hasCulturalRole
chosen
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
-
B.
familyCulturalRole
Indicates the role or function an entity holds within a family context as defined or shaped by cultural norms and traditions.
-
C.
ethnographicRole
Indicates the role or function an entity holds within an ethnographic context, such as a cultural, social, or research-related position.
-
D.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
E.
roleInBabel
Indicates that an entity participates in the Babel project or system with a specific role or function.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:27 p.m.