Triple
T797516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Orthodox Church |
E17055
|
entity |
| Predicate | autocephalous |
P19159
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Georgian Orthodox Church, autocephalous, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autocephalous Context triple: [Georgian Orthodox Church, autocephalous, true]
-
A.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
B.
hasEcumenicalAgreementWith
Indicates that two religious organizations or denominations are formally bound by a mutual ecumenical agreement recognizing shared faith, cooperation, or unity.
-
C.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
D.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
E.
prelate
Indicates that an entity holds the office or role of a high-ranking clergy member within a religious hierarchy.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b342888190a344fe81a2c9f33c |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.