Triple
T27003730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermannsburg |
E680180
|
entity |
| Predicate | religiousDenominationDominant |
P2986
|
FINISHED |
| Object | Lutheran |
—
|
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: Lutheran | Statement: [Hermannsburg, religiousDenominationDominant, Lutheran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousDenominationDominant Context triple: [Hermannsburg, religiousDenominationDominant, Lutheran]
-
A.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
B.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
C.
religionDominantBranch
Indicates that one religious branch is the primary or most prevalent form of a broader religion within a given context or population.
-
D.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
E.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 6:59 a.m.