Triple
T34354167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mímir |
E881669
|
entity |
| Predicate | headSentTo |
P179122
|
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, headSentTo, Odin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headSentTo Context triple: [Mímir, headSentTo, Odin]
-
A.
headConfirmationBy
Indicates that one entity confirms, approves, or validates something in the capacity of a head, leader, or chief authority over it.
-
B.
headFrom
Indicates a relationship where one entity originates, leads, or directs movement or action from another entity as its starting point or source.
-
C.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
D.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
-
E.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:58 a.m.