Triple
T28179601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Side Presbyterians |
E715988
|
entity |
| Predicate | issueOfConflict |
P163904
|
FINISHED |
| Object | revivalist methods |
—
|
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: revivalist methods | Statement: [New Side Presbyterians, issueOfConflict, revivalist methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueOfConflict Context triple: [New Side Presbyterians, issueOfConflict, revivalist methods]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictTopic
chosen
Indicates that the entities are in conflict specifically regarding the referenced topic or issue.
-
C.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
-
D.
societalConflict
Indicates a relationship where groups or individuals within a society are in opposition or tension over values, resources, power, or social norms.
-
E.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 10:18 p.m.