Triple
T19053952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snotra |
E466340
|
entity |
| Predicate | roleAmongAesir |
P9987
|
FINISHED |
| Object | goddess of wisdom and courtesy |
—
|
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: goddess of wisdom and courtesy | Statement: [Snotra, roleAmongAesir, goddess of wisdom and courtesy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAmongAesir Context triple: [Snotra, roleAmongAesir, goddess of wisdom and courtesy]
-
A.
roleInThor
Indicates that an entity has a specific role or character assignment in the context of the work "Thor."
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
roleAfterRagnarök
Indicates the role, status, or function an entity will have after the events of Ragnarök have occurred.
-
D.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
E.
roleInTheWrathOfGod
Indicates that an entity has a specific role or participation in the event, concept, or narrative referred to as "the Wrath of God."
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc049f64819093ae9fda26a49bd2 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.