Triple
T797542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Orthodox Church |
E17055
|
entity |
| Predicate | christianizationOfGeorgia |
P4040
|
FINISHED |
| Object | 4th 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: 4th century | Statement: [Georgian Orthodox Church, christianizationOfGeorgia, 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: christianizationOfGeorgia Context triple: [Georgian Orthodox Church, christianizationOfGeorgia, 4th century]
-
A.
conversionToChristianityCentury
chosen
Indicates the century during which an entity underwent or was associated with a conversion to Christianity.
-
B.
renamedAsConstantinopleBy
Indicates that one entity changed the name of another entity to "Constantinople."
-
C.
hadNationalChurch
Indicates that a country or region recognized a particular church as its official or primary national religious institution.
-
D.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
E.
oldestChristianState
Indicates that the subject is recognized as the earliest or first established Christian state in comparison to other states.
- 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_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. |
Created at: March 1, 2026, 7:38 p.m.