Triple
T2980896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E80506
|
entity |
| Predicate | isMaterLectionis |
P44423
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Aleph, isMaterLectionis, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaterLectionis Context triple: [Aleph, isMaterLectionis, yes]
-
A.
hasLiturgicalReading
Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
-
B.
hasCatechism
Indicates that an entity possesses, is associated with, or includes a catechism (a formal summary of religious doctrine, typically in question-and-answer format).
-
C.
hasLiturgicalBook
Indicates that one entity possesses, uses, or is associated with a specific liturgical book in a religious or worship context.
-
D.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
E.
partOfMagisterium
Indicates that one entity belongs to, is included within, or constitutes a component of the magisterium of another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.