Triple
T399987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbyterian |
E9258
|
entity |
| Predicate | hasChurchPolity |
P6329
|
FINISHED |
| Object | presbyterian polity |
—
|
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: presbyterian polity | Statement: [Presbyterian, hasChurchPolity, presbyterian polity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChurchPolity Context triple: [Presbyterian, hasChurchPolity, presbyterian polity]
-
A.
ecclesiasticalPolity
Indicates the form, structure, and governing system by which a religious or church organization is administered and its authority is distributed.
-
B.
churchPolity
chosen
Indicates the form, structure, and governing system by which a church or religious community is organized and administered.
-
C.
churchProvince
Indicates that one entity is an ecclesiastical province to which the other entity (typically a church jurisdiction or diocese) belongs or is administratively subordinate.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
hadNationalChurch
Indicates that a country or region recognized a particular church as its official or primary national religious institution.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8e655c819081eff85c0ef55fa5 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.