Triple
T3647758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mjolnir |
E77342
|
entity |
| Predicate | associatedWithPantheon |
P5447
|
FINISHED |
| Object | Norse gods |
—
|
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: Norse gods | Statement: [Mjolnir, associatedWithPantheon, Norse gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPantheon Context triple: [Mjolnir, associatedWithPantheon, Norse gods]
-
A.
sharedPantheonWith
Indicates that two deities or mythological figures belong to or are worshiped within the same religious pantheon or mythological tradition.
-
B.
associatedWithPub
Indicates that an entity has a connection or relationship with a particular publication (e.g., as source, reference, or related work).
-
C.
hasPantheonName
chosen
Indicates that an entity is associated with a specific pantheon and is identified by the given pantheon name.
-
D.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
E.
positionInPantheon
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38aa2388190bf1af926375e2433 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.