Triple
T4352397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbyterian–Independent conflict |
E98056
|
entity |
| Predicate | IndependentGoal |
P55716
|
FINISHED |
| Object | congregational autonomy |
—
|
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: congregational autonomy | Statement: [Presbyterian–Independent conflict, IndependentGoal, congregational autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndependentGoal Context triple: [Presbyterian–Independent conflict, IndependentGoal, congregational autonomy]
-
A.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
B.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
C.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
D.
goalStructure
Indicates the overarching objective or intended outcome that organizes and guides the structure of related actions, components, or relationships.
-
E.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.