Triple
T35424693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaffa Templer Colony |
E1023886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German Protestant settlement |
C61183
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: German Protestant settlement Context triple: [Jaffa Templer Colony, instanceOf, German Protestant settlement]
-
A.
German Lutheran
A German Lutheran is an adherent of the Lutheran branch of Protestant Christianity whose religious identity and practices are shaped by the theological heritage of Martin Luther within the cultural and historical context of Germany.
-
B.
Moravian settlement
A Moravian settlement is a planned religious community established by the Moravian Church, characterized by communal living, shared economic enterprises, and a strong emphasis on worship, education, and missionary work.
-
C.
Protestant enclave
chosen
A Protestant enclave is a geographically or socially distinct area where Protestant Christians form a concentrated majority, maintaining their religious, cultural, and institutional practices within a broader non-Protestant context.
-
D.
Puritan settlement
A Puritan settlement is a religiously motivated colonial community organized around strict moral codes, communal labor, and governance rooted in Puritan interpretations of Christianity.
-
E.
Swiss immigrant colony
A Swiss immigrant colony is a settlement established by Swiss migrants in a foreign country, typically organized around shared language, culture, and mutual economic or social support.
- F. None of above.
Provenance (1 batch)
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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.