Triple
T623869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Catholic Church of Slovakia |
E14571
|
entity |
| Predicate | recognizesOrders |
P17822
|
FINISHED |
| Object | historic episcopate |
—
|
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: historic episcopate | Statement: [Old Catholic Church of Slovakia, recognizesOrders, historic episcopate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesOrders Context triple: [Old Catholic Church of Slovakia, recognizesOrders, historic episcopate]
-
A.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
D.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
E.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e41753881909f0faed720cc31bc |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e2107548190af0c1d67cfa475d1 |
completed | March 1, 2026, 8:14 p.m. |
Created at: March 1, 2026, 7:35 p.m.