Triple
T1383231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Constitution Humanae Salutis |
E29385
|
entity |
| Predicate | documentForm |
P27217
|
FINISHED |
| Object | apostolic constitution |
—
|
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: apostolic constitution | Statement: [Apostolic Constitution Humanae Salutis, documentForm, apostolic constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentForm Context triple: [Apostolic Constitution Humanae Salutis, documentForm, apostolic constitution]
-
A.
documentModel
Indicates that an entity serves as or is associated with a specific structured representation or schema of a document.
-
B.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
C.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
D.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
E.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3377b608190b915e6871c1fe86e |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.