Triple
T30244500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | usedInEcclesiasticalLatin |
P143136
|
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: [Spira, usedInEcclesiasticalLatin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEcclesiasticalLatin Context triple: [Spira, usedInEcclesiasticalLatin, true]
-
A.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
B.
isEcclesiasticalFormOf
Indicates that one term is the ecclesiastical (church-related or liturgical) form or variant of another term.
-
C.
ecclesialUse
chosen
Indicates that something is used, practiced, or applied within an ecclesial (church or religious institutional) context.
-
D.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
E.
differsFromLatinChurchIn
Indicates that one church or tradition is distinct from the Latin Church in some doctrinal, liturgical, canonical, or organizational aspect.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:39 p.m.