Triple
T32446663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustinian Canons monastery |
E829165
|
entity |
| Predicate | vowsOrPromises |
P173104
|
FINISHED |
| Object | stability in community |
—
|
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: stability in community | Statement: [Augustinian Canons monastery, vowsOrPromises, stability in community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowsOrPromises Context triple: [Augustinian Canons monastery, vowsOrPromises, stability in community]
-
A.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
B.
vowsAre
chosen
Indicates that one entity makes or holds a solemn promise or commitment toward another entity.
-
C.
vowsRequired
Indicates that a formal promise, oath, or commitment is mandated to proceed with or validate the associated relationship or action.
-
D.
definesVows
Indicates that an entity establishes or specifies the content, terms, or wording of vows for another entity or situation.
-
E.
makesPromisesOf
Indicates that one entity commits or assures a future action, benefit, or outcome to another entity.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e66478819086a588340ec05a53 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.