Triple
T28179644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Side–New Side controversy |
E715989
|
entity |
| Predicate | reunifiedAs |
P164410
|
FINISHED |
| Object | Synod of New York and Philadelphia |
—
|
NE NERFINISHED |
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: Synod of New York and Philadelphia | Statement: [Old Side–New Side controversy, reunifiedAs, Synod of New York and Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reunifiedAs Context triple: [Old Side–New Side controversy, reunifiedAs, Synod of New York and Philadelphia]
-
A.
reunitedAs
Indicates that entities who were previously separated have come back together or been brought back into association.
-
B.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
reunitedFor
Indicates that entities who were previously separated have come back together or been brought back into association.
-
E.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 10:18 p.m.