Triple

T11474900
Position Surface form Disambiguated ID Type / Status
Subject Crucifixus E272000 entity
Predicate liturgicalTextSection P12432 FINISHED
Object Et incarnatus est – Crucifixus – Et resurrexit 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: Et incarnatus est – Crucifixus – Et resurrexit | Statement: [Crucifixus, liturgicalTextSection, Et incarnatus est – Crucifixus – Et resurrexit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: liturgicalTextSection
Context triple: [Crucifixus, liturgicalTextSection, Et incarnatus est – Crucifixus – Et resurrexit]
  • A. liturgicalText chosen
    Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
  • B. liturgicalTextsFoundIn
    Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
  • C. liturgicalSequence
    Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
  • D. liturgicalMoment
    Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
  • E. liturgicalSetting
    Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
  • 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8294c8dc48190a515f83c99405a3b completed April 9, 2026, 10:33 p.m.
PD Predicate disambiguation batch_69d8086ecd6c81908f424864857762d6 completed April 9, 2026, 8:13 p.m.
Created at: April 8, 2026, 9:36 p.m.