Triple
T2612672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin Evangelical Lutheran Synod |
E58811
|
entity |
| Predicate | clergyCountEstimate |
P41419
|
FINISHED |
| Object | over 1000 pastors |
—
|
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: over 1000 pastors | Statement: [Wisconsin Evangelical Lutheran Synod, clergyCountEstimate, over 1000 pastors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyCountEstimate Context triple: [Wisconsin Evangelical Lutheran Synod, clergyCountEstimate, over 1000 pastors]
-
A.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
B.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
C.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
-
D.
hasNumberOfChurches
Indicates the relationship that specifies how many churches are associated with a given entity.
-
E.
priestsCalled
Indicates that one or more individuals are given the role, title, or vocation of priest, typically through a formal or divine calling.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:50 p.m.