Triple
T29421162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Häme |
E746158
|
entity |
| Predicate | preChristianCulture |
P167159
|
FINISHED |
| Object | Finnic paganism |
—
|
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: Finnic paganism | Statement: [Häme, preChristianCulture, Finnic paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preChristianCulture Context triple: [Häme, preChristianCulture, Finnic paganism]
-
A.
preChristianOrigin
Indicates that something originated or came into existence before the advent or establishment of Christianity.
-
B.
preIslamicReligion
Indicates that an entity practiced, adhered to, or was associated with a religious belief system that existed before the advent or spread of Islam.
-
C.
religionInPreRomanPeriod
Indicates the religion or belief system practiced in a place or by a group during the period before Roman rule.
-
D.
preRomanCulturalInfluence
Indicates that one culture exerted influence on another during the period before Roman dominance or rule.
-
E.
religionInEarlyPeriod
Indicates that an entity had a particular religious affiliation or practice during its early or initial historical period.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a68fedc8190ab94d22edc6ff90b |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:05 p.m.