Triple
T25678748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist Churches in Northern India |
E643878
|
entity |
| Predicate | churchUnionPartner |
P13041
|
FINISHED |
| Object | Church of North India |
—
|
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: Church of North India | Statement: [Baptist Churches in Northern India, churchUnionPartner, Church of North India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchUnionPartner Context triple: [Baptist Churches in Northern India, churchUnionPartner, Church of North India]
-
A.
churchCommunion
Indicates a relationship in which an individual or group participates in or is in fellowship with a particular church community or denomination.
-
B.
associatedWithChurch
chosen
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
C.
churchFunction
Indicates the role, purpose, or function that a church serves in relation to its activities, community, or religious practices.
-
D.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
E.
missionaryOrganization
Indicates that an entity is a religious or faith-based organization dedicated to missionary work or activities.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb77c3a08190b63e811dd21989fd |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:43 p.m.