Triple
T24048719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of the Scala Sancta |
E595592
|
entity |
| Predicate | accessRuleForHolyStairs |
P154667
|
FINISHED |
| Object | climbed only on knees |
—
|
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: climbed only on knees | Statement: [Sanctuary of the Scala Sancta, accessRuleForHolyStairs, climbed only on knees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRuleForHolyStairs Context triple: [Sanctuary of the Scala Sancta, accessRuleForHolyStairs, climbed only on knees]
-
A.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
B.
elevationRelativeToBasilicaFloor
Indicates the vertical height or depth of something measured relative to the level of the basilica’s floor.
-
C.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
ossuaryAccess
Indicates that an entity has permission or ability to enter, use, or otherwise gain access to an ossuary.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cedaa08190bf54857de1b312ed |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:18 p.m.