Triple
T25678965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican dioceses of northern India |
E643883
|
entity |
| Predicate | unionProcess |
P13846
|
FINISHED |
| Object | formation of Church of North India in 1970 |
—
|
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: formation of Church of North India in 1970 | Statement: [Anglican dioceses of northern India, unionProcess, formation of Church of North India in 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionProcess Context triple: [Anglican dioceses of northern India, unionProcess, formation of Church of North India in 1970]
-
A.
unionForm
Indicates that an entity is a form, document, or process used to establish, join, or manage membership in a union or union-related organization.
-
B.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
C.
unionEntry
Indicates that an entity is a member or participant in a specific union or collective organization.
-
D.
unionEvent
chosen
Indicates an event in which two or more entities are joined or combined into a single unified whole.
-
E.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
- 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:44 p.m.