Triple
T11583691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Evangelical Lutheran Church |
E274695
|
entity |
| Predicate | mergerProcess |
P75658
|
FINISHED |
| Object | denominational consolidation |
—
|
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: denominational consolidation | Statement: [American Evangelical Lutheran Church, mergerProcess, denominational consolidation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerProcess Context triple: [American Evangelical Lutheran Church, mergerProcess, denominational consolidation]
-
A.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
B.
mergerMethod
chosen
Indicates the method or process by which two or more entities are combined or merged into a single entity.
-
C.
mergedByProcess
Indicates that one or more entities are combined or unified as the result of a specific process.
-
D.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
E.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904db5748190ae5f10ae86ccdf46 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.