Triple
T10626850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Váli |
E250345
|
entity |
| Predicate | birthPurpose |
P5256
|
FINISHED |
| Object | to avenge Baldr |
—
|
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: to avenge Baldr | Statement: [Váli, birthPurpose, to avenge Baldr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthPurpose Context triple: [Váli, birthPurpose, to avenge Baldr]
-
A.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
reasonForCreation
chosen
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
C.
purposeOfPlacement
Indicates that something has been placed or positioned with the specific aim, function, or intended use of that placement.
-
D.
motiveForAdoption
Indicates that one entity serves as the reason or motivation for another entity’s act of adopting something (such as a person, practice, or object).
-
E.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:55 p.m.