Triple
T34162268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hati |
E876308
|
entity |
| Predicate | regionOfWorshipOrBelief |
P23627
|
FINISHED |
| Object | Scandinavia |
—
|
NE NERFINISHED |
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: Scandinavia | Statement: [Hati, regionOfWorshipOrBelief, Scandinavia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfWorshipOrBelief Context triple: [Hati, regionOfWorshipOrBelief, Scandinavia]
-
A.
majorRegionOfWorship
chosen
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
B.
traditionalReligionPlace
Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
-
C.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
-
E.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 1, 2026, 1:54 a.m.