Triple
T28072661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lay Dominicans |
E709447
|
entity |
| Predicate | makesPromisesOf |
P10241
|
FINISHED |
| Object | living according to the Rule |
—
|
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: living according to the Rule | Statement: [Lay Dominicans, makesPromisesOf, living according to the Rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesPromisesOf Context triple: [Lay Dominicans, makesPromisesOf, living according to the Rule]
-
A.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
B.
includesPromiseOf
Indicates that one entity contains or entails a commitment or assurance to perform or provide something to another entity.
-
C.
hasPromiseType
Indicates that an entity is associated with, or classified by, a specific type or category of promise.
-
D.
promisesAttributed
Indicates that a commitment or promise is ascribed to a particular entity as its source or author.
-
E.
corePromise
chosen
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
- 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_69f6403d696081909ff86d174e014d11 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:47 p.m.