Triple
T3532586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomos of autocephaly for the Orthodox Church of Ukraine |
E74693
|
entity |
| Predicate | dateHandedOver |
P48144
|
FINISHED |
| Object | 2019-01-06 |
—
|
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: 2019-01-06 | Statement: [Tomos of autocephaly for the Orthodox Church of Ukraine, dateHandedOver, 2019-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateHandedOver Context triple: [Tomos of autocephaly for the Orthodox Church of Ukraine, dateHandedOver, 2019-01-06]
-
A.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
C.
UNSeatTransferDate
Indicates the date on which a seat is transferred from one holder to another.
-
D.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
E.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9a14c881908932b17ed3eececb |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed7f2ec819085467d281712e0e8 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.