Triple
T7120327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of North India |
E165931
|
entity |
| Predicate | ministryStructure |
P74964
|
FINISHED |
| Object | bishops, presbyters and deacons |
—
|
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: bishops, presbyters and deacons | Statement: [Church of North India, ministryStructure, bishops, presbyters and deacons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ministryStructure Context triple: [Church of North India, ministryStructure, bishops, presbyters and deacons]
-
A.
ministry
Indicates that an entity serves as a governmental ministry responsible for specific public functions or policy areas in relation to another entity.
-
B.
numberOfMinistries
Indicates the total count of ministries associated with or belonging to a given entity.
-
C.
formedAsMinistry
Indicates that an organization or body was created or established in the form of a ministry.
-
D.
viewOfMinistry
Indicates a relationship where something presents or provides a visual perspective of a ministry or governmental department.
-
E.
hasMinistries
Indicates that an entity possesses, oversees, or is organized into one or more ministries as subordinate units or departments.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61ca6a88190a0eb9f287e3b723c |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:43 p.m.