Triple
T10805135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muninn |
E254941
|
entity |
| Predicate | oftenDepictedPerchedOn |
P34220
|
FINISHED |
| Object | Odin's shoulders |
—
|
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: Odin's shoulders | Statement: [Muninn, oftenDepictedPerchedOn, Odin's shoulders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDepictedPerchedOn Context triple: [Muninn, oftenDepictedPerchedOn, Odin's shoulders]
-
A.
hasPerchDepicted
Indicates that a perch (such as a resting place or support for an animal or object) is visually represented or shown in association with the subject.
-
B.
oftenDepictedAs
Indicates that one entity is frequently represented or portrayed in the form, appearance, or symbolism of another entity.
-
C.
commonlyDepictedOn
chosen
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
D.
depictedAbove
Indicates that one entity is visually represented in an image, illustration, or diagram that is positioned above another referenced element in a layout or document.
-
E.
oftenSits
Indicates that an entity frequently assumes a sitting position, either habitually or on many occasions.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733726e2881908d4fe2cfe046ab43 |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.