Triple
T34292622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valkyries |
E879931
|
entity |
| Predicate | taskInValhalla |
P107993
|
FINISHED |
| Object | Serve mead to 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 mead to the einherjar | Statement: [Valkyries, taskInValhalla, Serve mead to the einherjar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskInValhalla Context triple: [Valkyries, taskInValhalla, Serve mead to the einherjar]
-
A.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
B.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
C.
typicalTask
chosen
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
-
D.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
E.
taskDomain
Indicates that a task belongs to, is categorized under, or is associated with a particular domain or area of activity.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.