Triple
T2340660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Greek Catholic Church |
E45017
|
entity |
| Predicate | unionWithRomeYear |
P4318
|
FINISHED |
| Object | 1596 |
—
|
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: 1596 | Statement: [Ukrainian Greek Catholic Church, unionWithRomeYear, 1596]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionWithRomeYear Context triple: [Ukrainian Greek Catholic Church, unionWithRomeYear, 1596]
-
A.
unificationDate
chosen
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
B.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
C.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
D.
hasEcumenicalAgreementWith
Indicates that two religious organizations or denominations are formally bound by a mutual ecumenical agreement recognizing shared faith, cooperation, or unity.
-
E.
dynasticUnion
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.