Triple
T3619734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laetare Jerusalem |
E76692
|
entity |
| Predicate | ecclesiasticalGenre |
P50480
|
FINISHED |
| Object | magisterial document |
—
|
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: magisterial document | Statement: [Laetare Jerusalem, ecclesiasticalGenre, magisterial document]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecclesiasticalGenre Context triple: [Laetare Jerusalem, ecclesiasticalGenre, magisterial document]
-
A.
liturgicalGenre
Indicates the specific type or category of liturgical text, music, or ritual to which something belongs.
-
B.
religiousGenre
Indicates that the subject is associated with or categorized under a religious genre, style, or tradition.
-
C.
ecclesiasticalStyle
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
-
D.
ecclesiasticalDocumentOf
Indicates that one entity is an ecclesiastical (church-related) document that is issued by, belongs to, or is formally associated with another entity.
-
E.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b85f6c819091000e231d9dac87 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.