Triple
T6950261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Church (New York City) |
E160900
|
entity |
| Predicate | congregationFounded |
P74245
|
FINISHED |
| Object | 1808 |
—
|
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: 1808 | Statement: [Grace Church (New York City), congregationFounded, 1808]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congregationFounded Context triple: [Grace Church (New York City), congregationFounded, 1808]
-
A.
establishedAsCongregationBy
Indicates that an entity was formally created or organized as a congregation by another specified agent or authority.
-
B.
originalCongregationName
Indicates the name by which a congregation was originally known before any later changes or renamings.
-
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.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
E.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dacb524c81909aade2282a4c0c01 |
completed | March 27, 2026, 7:30 p.m. |
Created at: March 27, 2026, 2:29 p.m.