Triple
T13261148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallican Rite |
E315796
|
entity |
| Predicate | liturgicalBookType |
P3101
|
FINISHED |
| Object | missal |
—
|
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: missal | Statement: [Gallican Rite, liturgicalBookType, missal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalBookType Context triple: [Gallican Rite, liturgicalBookType, missal]
-
A.
hasLiturgicalBook
chosen
Indicates that one entity possesses, uses, or is associated with a specific liturgical book in a religious or worship context.
-
B.
liturgicalGenre
Indicates the specific type or category of liturgical text, music, or ritual to which something belongs.
-
C.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
D.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
E.
liturgicalTextsFoundIn
Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.