Triple
T22587738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehonians |
E564845
|
entity |
| Predicate | hasAdditionalVowOrPromise |
P7683
|
FINISHED |
| Object | availability for the mission of the Church |
—
|
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: availability for the mission of the Church | Statement: [Dehonians, hasAdditionalVowOrPromise, availability for the mission of the Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalVowOrPromise Context triple: [Dehonians, hasAdditionalVowOrPromise, availability for the mission of the Church]
-
A.
fulfilledVow
Indicates that an entity has carried out or honored a previously made vow or promise.
-
B.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
C.
additionalVow
chosen
Indicates that an entity makes or is associated with an extra or supplementary vow beyond an initial or primary vow.
-
D.
hasTypeOfVows
Indicates that one entity is characterized by or associated with a particular kind or category of vows.
-
E.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615de7d48190b1ca46c76a1e609c |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:46 p.m.