Triple
T28072663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lay Dominicans |
E709447
|
entity |
| Predicate | makesPromisesOf |
P164022
|
FINISHED |
| Object | regular participation in the sacraments |
—
|
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: regular participation in the sacraments | Statement: [Lay Dominicans, makesPromisesOf, regular participation in the sacraments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesPromisesOf Context triple: [Lay Dominicans, makesPromisesOf, regular participation in the sacraments]
-
A.
makesPromisesOf
chosen
Indicates that one entity commits or assures a future action, benefit, or outcome to another entity.
-
B.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
C.
includesPromiseOf
Indicates that one entity contains or entails a commitment or assurance to perform or provide something to another entity.
-
D.
hasPromiseType
Indicates that an entity is associated with, or classified by, a specific type or category of promise.
-
E.
promisesAttributed
Indicates that a commitment or promise is ascribed to a particular entity as its source or author.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:47 p.m.