Triple
T15475463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic paganism |
E376771
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Perkūnas |
E783927
|
NE 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: Perkūnas | Statement: [Baltic paganism, hasDeity, Perkūnas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perkūnas Context triple: [Baltic paganism, hasDeity, Perkūnas]
-
A.
Perkūnas
chosen
Perkūnas is the thunder and sky god of Baltic mythology, revered as a chief deity associated with storms, justice, and warfare.
-
B.
Ukko
Ukko is the chief sky and thunder god in Finnish mythology, associated with weather, harvests, and the protection of people.
-
C.
Svetovid
Svetovid is a major Slavic deity, often depicted with four heads and associated with war, abundance, and prophecy.
-
D.
Hodr
Hodr is a blind god in Norse mythology, best known for being tricked into killing his brother Baldr.
-
E.
Hoderi
Hoderi is a deity in Japanese mythology, known as the elder son of Ninigi-no-Mikoto and an ancestor of seafaring clans.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6e859481909c3d08343b7ad27c |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d093ccc8190aefc355a837c83f4 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:34 a.m.