Triple
T3190158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syriac Catholic Church |
E66801
|
entity |
| Predicate | unionWithRomeRestored |
P38778
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Syriac Catholic Church, unionWithRomeRestored, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionWithRomeRestored Context triple: [Syriac Catholic Church, unionWithRomeRestored, 17th century]
-
A.
unionWithRomeConcludedAt
chosen
Indicates that the formal union with Rome was concluded or established at a specific place or time.
-
B.
reunionWithRomeProclaimedBy
Indicates that a reunion with Rome was formally announced or declared by a specific agent or authority.
-
C.
reunionWithRomeLedBy
Indicates that a reunion or restoration of union with Rome is carried out under the leadership or guidance of a specified person or authority.
-
D.
reunionWithRomeFormalizedBy
Indicates that a reunion or restoration of relations with Rome is officially established or made binding through a specific formal act, agreement, or document.
-
E.
yearOfEdictOfRestitution
Indicates the specific calendar year in which the Edict of Restitution was issued.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e67e948190afbd9cc6a3ade415 |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.