Triple
T8277597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilian Salvatorian Order |
E193584
|
entity |
| Predicate | hasMainCharism |
P57647
|
FINISHED |
| Object | pastoral work |
—
|
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: pastoral work | Statement: [Basilian Salvatorian Order, hasMainCharism, pastoral work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharism Context triple: [Basilian Salvatorian Order, hasMainCharism, pastoral work]
-
A.
sharesCharismWith
Indicates that two entities possess and express the same or very similar spiritual gift, mission, or distinctive inspirational quality.
-
B.
hasCharm
Indicates that an entity possesses or exhibits charm, attractiveness, or an appealing quality.
-
C.
foundingCharism
chosen
Indicates the distinctive spiritual focus, mission, or guiding gift that characterizes the founding identity of a religious community or organization.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
hasMainVisionary
Indicates that one entity serves as the primary creative or strategic visionary responsible for guiding or shaping 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ea3fb481908b59414702a5147e |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.