Triple
T2584918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Letter Concerning Toleration |
E57175
|
entity |
| Predicate | positionOnChurchPower |
P40523
|
FINISHED |
| Object | the church should not wield coercive civil power |
—
|
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: the church should not wield coercive civil power | Statement: [A Letter Concerning Toleration, positionOnChurchPower, the church should not wield coercive civil power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnChurchPower Context triple: [A Letter Concerning Toleration, positionOnChurchPower, the church should not wield coercive civil power]
-
A.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
E.
viewOnChurch
Indicates that something has a view overlooking or directed toward a church.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cd07588190b3cb8cc348f12938 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.