Triple
T3441887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valkyries |
E72582
|
entity |
| Predicate | dutyInValhalla |
P48830
|
FINISHED |
| Object | Serve the Einherjar |
—
|
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: Serve the Einherjar | Statement: [Valkyries, dutyInValhalla, Serve the Einherjar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutyInValhalla Context triple: [Valkyries, dutyInValhalla, Serve the Einherjar]
-
A.
garrisonDuty
Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
legendaryDeath
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
D.
deathEmpire
Indicates a relationship where an empire causes, is associated with, or is characterized by widespread death or destruction.
-
E.
primacyOfHonorOver
Indicates that one entity is regarded as having higher honor, status, or precedence than another.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba276b708190949f294a8d09ec7b |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:16 p.m.