Triple
T3480035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niflheim |
E73466
|
entity |
| Predicate | afterlifeFunction |
P44744
|
FINISHED |
| Object | abode of some of the dead |
—
|
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: abode of some of the dead | Statement: [Niflheim, afterlifeFunction, abode of some of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterlifeFunction Context triple: [Niflheim, afterlifeFunction, abode of some of the dead]
-
A.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
B.
afterlifeForm
chosen
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
-
C.
laterFunction
Indicates that one function or event occurs after another in time.
-
D.
endedActivityAfterDeathOf
Indicates that an activity was terminated following, and as a consequence of, the death of a specified entity.
-
E.
coffinLaterBecomes
Indicates that something which is initially a coffin later transforms into or is repurposed as another object or state.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb7461708190898002fbd1191f34 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.