Triple
T33637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy See |
E670
|
entity |
| Predicate | issuesDocumentType |
P1557
|
FINISHED |
| Object | papal encyclical |
—
|
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: papal encyclical | Statement: [Holy See, issuesDocumentType, papal encyclical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesDocumentType Context triple: [Holy See, issuesDocumentType, papal encyclical]
-
A.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
B.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
C.
issues
chosen
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
E.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.