Triple
T34161645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhrimnir |
E876291
|
entity |
| Predicate | preparesFoodFor |
P178458
|
FINISHED |
| Object | einherjar |
—
|
NE NERFINISHED |
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: einherjar | Statement: [Andhrimnir, preparesFoodFor, einherjar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparesFoodFor Context triple: [Andhrimnir, preparesFoodFor, einherjar]
-
A.
typeOfPreparation
Indicates the method or process by which something is prepared or made ready for use, consumption, or further action.
-
B.
commonlyPreparedFor
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
-
C.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
D.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
intendedFood
Indicates that one entity is the food item that another entity plans or is meant to eat or consume.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:54 a.m.