Triple
T5955028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark the Monk |
E132490
|
entity |
| Predicate | spiritualPracticeTaught |
P12791
|
FINISHED |
| Object | unceasing prayer |
—
|
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: unceasing prayer | Statement: [Mark the Monk, spiritualPracticeTaught, unceasing prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualPracticeTaught Context triple: [Mark the Monk, spiritualPracticeTaught, unceasing prayer]
-
A.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
B.
spiritualAchievement
Indicates the attainment or realization of a significant level of spiritual growth, insight, or enlightenment by an entity.
-
C.
spiritualDiscipline
chosen
Indicates a relationship where an entity engages in or practices a form of spiritual training, exercise, or regimen aimed at cultivating spiritual growth or character.
-
D.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
-
E.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.