Triple
T35536544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavia |
E1026944
|
entity |
| Predicate | usedInEcclesiasticalDocuments |
P143136
|
FINISHED |
| Object | Church Slavonic |
—
|
NE NERFINISHED |
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: Church Slavonic | Statement: [Moldavia, usedInEcclesiasticalDocuments, Church Slavonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEcclesiasticalDocuments Context triple: [Moldavia, usedInEcclesiasticalDocuments, Church Slavonic]
-
A.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
B.
ecclesialUse
chosen
Indicates that something is used, practiced, or applied within an ecclesial (church or religious institutional) context.
-
C.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
D.
ecclesiasticalDocumentOf
Indicates that one entity is an ecclesiastical (church-related) document that is issued by, belongs to, or is formally associated with another entity.
-
E.
usedInChristianTradition
Indicates that something is employed, practiced, or recognized within Christian religious beliefs, rituals, or cultural traditions.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:04 p.m.