Triple
T11005757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Archiepiscopal Church |
E260113
|
entity |
| Predicate | synodCompetenceIncludes |
P96961
|
FINISHED |
| Object | erection of eparchies within its territory |
—
|
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: erection of eparchies within its territory | Statement: [Major Archiepiscopal Church, synodCompetenceIncludes, erection of eparchies within its territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synodCompetenceIncludes Context triple: [Major Archiepiscopal Church, synodCompetenceIncludes, erection of eparchies within its territory]
-
A.
hasSynod
Indicates that an entity is associated with, governed by, or participates in a particular synod (a formal ecclesiastical council or assembly).
-
B.
synodPurpose
Indicates that a synod is convened or exists for a particular purpose, goal, or intended function.
-
C.
hasSynodMembers
Indicates that a synod includes or is composed of the specified members.
-
D.
typeOfSynod
Indicates the specific kind or category to which a particular synod belongs.
-
E.
numberOfSynods
Indicates the count of synods associated with or held by a given entity.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d733b27ffc81908ab1b8df198cd5c7 |
completed | April 9, 2026, 5:05 a.m. |
Created at: April 8, 2026, 9:25 p.m.