Triple
T8277621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilian Salvatorian Order |
E193584
|
entity |
| Predicate | hasEvangelizationActivity |
P19746
|
FINISHED |
| Object | youth ministry |
—
|
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: youth ministry | Statement: [Basilian Salvatorian Order, hasEvangelizationActivity, youth ministry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvangelizationActivity Context triple: [Basilian Salvatorian Order, hasEvangelizationActivity, youth ministry]
-
A.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
B.
hasNotableMissionary
Indicates that an entity is associated with, or has, a notable missionary linked to it.
-
C.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasLiturgicalCelebration
Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
-
E.
hasPastoralMission
Indicates that an entity is responsible for providing spiritual care, guidance, or religious leadership to a community or group.
- 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.