Triple
T2302225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laborem Exercens |
E51757
|
entity |
| Predicate | magisterialRank |
P38628
|
FINISHED |
| Object | encyclical letter |
—
|
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: encyclical letter | Statement: [Laborem Exercens, magisterialRank, encyclical letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magisterialRank Context triple: [Laborem Exercens, magisterialRank, encyclical letter]
-
A.
magisterialStatus
Indicates that an entity holds or is assigned a formal magisterial (official judicial or administrative) authority or status in relation to another entity or context.
-
B.
magisterialType
Indicates the specific kind or category of magisterial authority, jurisdiction, or court associated with an entity.
-
C.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
D.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcbab15488190bc8d2345f9d9f2bd |
completed | March 7, 2026, 6:54 a.m. |
Created at: March 4, 2026, 7:49 p.m.