Triple
T8217175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Brothers |
E191961
|
entity |
| Predicate | vowedEvangelicalCounsels |
P62759
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Christian Brothers, vowedEvangelicalCounsels, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowedEvangelicalCounsels Context triple: [Christian Brothers, vowedEvangelicalCounsels, poverty]
-
A.
requiresEvangelicalCounsels
Indicates that one entity is obligated to observe or adhere to the evangelical counsels (typically poverty, chastity, and obedience) in relation to another entity or context.
-
B.
vowedVirtue
chosen
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
-
C.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
D.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
E.
spiritualMinistry
Indicates that one entity provides religious or spiritual guidance, care, or services 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776f41108190bed1c6a8ddbea374 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.