Triple
T6442499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scala Sancta |
E138257
|
entity |
| Predicate | devotionalAct |
P68203
|
FINISHED |
| Object | 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: penance | Statement: [Scala Sancta, devotionalAct, penance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalAct Context triple: [Scala Sancta, devotionalAct, penance]
-
A.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
B.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
C.
devotionalPracticesInclude
chosen
Indicates that certain devotional practices form a part or subset of a broader set of devotional activities associated with an entity.
-
D.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
E.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.