Triple
T2998944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old South Church |
E81138
|
entity |
| Predicate | foundedAsCongregation |
P364
|
FINISHED |
| Object | 1669 |
—
|
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: 1669 | Statement: [Old South Church, foundedAsCongregation, 1669]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCongregation Context triple: [Old South Church, foundedAsCongregation, 1669]
-
A.
establishedAsCongregationBy
Indicates that an entity was formally created or organized as a congregation by another specified agent or authority.
-
B.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
D.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
-
E.
religiousAffiliationAtFoundation
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.