Triple
T18141945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbyterian party |
E434283
|
entity |
| Predicate | hadPositionOnChurchPolity |
P40523
|
FINISHED |
| Object | rejection of episcopacy |
—
|
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: rejection of episcopacy | Statement: [Presbyterian party, hadPositionOnChurchPolity, rejection of episcopacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPositionOnChurchPolity Context triple: [Presbyterian party, hadPositionOnChurchPolity, rejection of episcopacy]
-
A.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
positionOnChurchPower
chosen
Indicates a stance or viewpoint regarding the extent, role, or legitimacy of church authority or power.
-
C.
hasChurchmanship
Indicates that an entity adheres to or is associated with a particular style, tradition, or practice within a Christian church.
-
D.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
E.
seatOfChurchLeadership
Indicates the location that serves as the central administrative or authoritative base for a church’s leadership.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0c8aa88190b4ded7e6d05f6edf |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.