Triple
T16950492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Тризуб |
E411167
|
entity |
| Predicate | religiousInterpretation |
P5494
|
FINISHED |
| Object | symbol of the Holy Trinity |
—
|
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: symbol of the Holy Trinity | Statement: [Тризуб, religiousInterpretation, symbol of the Holy Trinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousInterpretation Context triple: [Тризуб, religiousInterpretation, symbol of the Holy Trinity]
-
A.
theologicalInterpretation
chosen
Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
-
B.
religiousTopicAddressed
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
religiousTextTradition
Indicates that a religious text is associated with, originates from, or is authoritative within a particular religious tradition or denomination.
-
E.
religiousTextCategory
Indicates that a religious text belongs to or is classified under a particular category or type.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb6e5fc8190b1bd3ad1c2773685 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.