Triple
T8041470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite Synod of Bishops |
E187449
|
entity |
| Predicate | typeOfSynod |
P80703
|
FINISHED |
| Object | patriarchal synod |
—
|
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: patriarchal synod | Statement: [Maronite Synod of Bishops, typeOfSynod, patriarchal synod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSynod Context triple: [Maronite Synod of Bishops, typeOfSynod, patriarchal synod]
-
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.
hasSynodicalGovernment
Indicates that an entity is governed or administered through a synodical (council-based, typically ecclesiastical) system of decision-making.
-
D.
relatedSynod
Indicates a relationship where one entity is associated with, connected to, or involved in the same synod (a formal ecclesiastical council or assembly) as another entity.
-
E.
postSynodal
Indicates a relationship or action that occurs after, or as a consequence of, a synod or synodal decision.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1e98508190a29a7bb5055f8ba0 |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:23 p.m.