Triple
T626411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Orthodox Church |
E15828
|
entity |
| Predicate | followsChristology |
P5493
|
FINISHED |
| Object | Chalcedonian |
—
|
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: Chalcedonian | Statement: [Serbian Orthodox Church, followsChristology, Chalcedonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsChristology Context triple: [Serbian Orthodox Church, followsChristology, Chalcedonian]
-
A.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
B.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
C.
emphasizesAttributeOfChrist
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Christ.
-
D.
theologicalCategory
chosen
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
E.
theologicalContext
Indicates the religious or doctrinal framework, tradition, or set of beliefs within which something (such as a text, event, or concept) is interpreted or understood.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e587c448190987943a6aad209d1 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.