Triple
T375731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Penitentiary |
E8367
|
entity |
| Predicate | hasTypeOfSecrecy |
P13085
|
FINISHED |
| Object | pontifical secret |
—
|
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: pontifical secret | Statement: [Apostolic Penitentiary, hasTypeOfSecrecy, pontifical secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSecrecy Context triple: [Apostolic Penitentiary, hasTypeOfSecrecy, pontifical secret]
-
A.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
C.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
D.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
E.
isWithheldBy
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96216048190873ae533fa5b864d |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ebcb1b2c8190a68bb3bad600c227 |
completed | Feb. 28, 2026, 1:21 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.