Triple
T34354168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mímir |
E881669
|
entity |
| Predicate | headPreservedBy |
P120371
|
FINISHED |
| Object | Odin |
—
|
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: Odin | Statement: [Mímir, headPreservedBy, Odin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headPreservedBy Context triple: [Mímir, headPreservedBy, Odin]
-
A.
headRetention
Indicates that an entity maintains or preserves its leadership, primary position, or top status over time or through a given event or process.
-
B.
hasPreserved
Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
-
C.
preservedFor
Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
-
D.
isPreservedBy
chosen
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
E.
headFrom
Indicates a relationship where one entity originates, leads, or directs movement or action from another entity as its starting point or source.
- 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_69f349bd06008190904c2f86c42749e3 |
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:58 a.m.