Triple
T20575266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De lapsis |
E505199
|
entity |
| Predicate | positionOnLapsed |
P93912
|
FINISHED |
| Object | allows reconciliation after suitable 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: allows reconciliation after suitable penance | Statement: [De lapsis, positionOnLapsed, allows reconciliation after suitable penance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLapsed Context triple: [De lapsis, positionOnLapsed, allows reconciliation after suitable penance]
-
A.
positionOnPast
Indicates that one entity occupied a specific position or location relative to another entity at some point in the past.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
D.
positionInLent
Indicates the specific point or stage an event, day, or period occupies within the overall timeline of Lent.
-
E.
positionOnOutcome
chosen
Indicates the stance or viewpoint an entity holds regarding a particular outcome or result.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a909785c8190a02b1195eadb384c |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.