Triple
T1312597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What I Believe |
E28026
|
entity |
| Predicate | positionOnChurch |
P4077
|
FINISHED |
| Object | rejects alliance of church and state |
—
|
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: rejects alliance of church and state | Statement: [What I Believe, positionOnChurch, rejects alliance of church and state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnChurch Context triple: [What I Believe, positionOnChurch, rejects alliance of church and state]
-
A.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
viewOnChurch
Indicates that something has a view overlooking or directed toward a church.
-
C.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
D.
viewOnChurchState
chosen
Indicates a stance or opinion an entity holds regarding the proper relationship between religious institutions and governmental authority.
-
E.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1572b1c8190ab978198c2d655c8 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.