Triple
T33062149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Cornelius |
E846000
|
entity |
| Predicate | policyOnLapsed |
P182433
|
FINISHED |
| Object | readmission after penance |
—
|
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: readmission after penance | Statement: [Pope Cornelius, policyOnLapsed, readmission after penance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyOnLapsed Context triple: [Pope Cornelius, policyOnLapsed, readmission after penance]
-
A.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
B.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
-
C.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
-
D.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
-
E.
isOnPolicy
Indicates that an action, configuration, or behavior complies with and adheres to a specified policy or set of rules.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 1, 2026, 1:25 a.m.