Triple
T6834842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dei Verbum |
E157422
|
entity |
| Predicate | hasDogmaticRank |
P10111
|
FINISHED |
| Object | dogmatic constitution |
—
|
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: dogmatic constitution | Statement: [Dei Verbum, hasDogmaticRank, dogmatic constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDogmaticRank Context triple: [Dei Verbum, hasDogmaticRank, dogmatic constitution]
-
A.
isDefinedAsDogmaBy
Indicates that one entity formally establishes or declares another entity as dogma or authoritative doctrine.
-
B.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
C.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
D.
doctrinalStatus
chosen
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
-
E.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67a9ff88190b0d86331b3ea06aa |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.