Triple
T10921773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redemptorists |
E257964
|
entity |
| Predicate | notableApostolate |
P96661
|
FINISHED |
| Object | popular parish missions |
—
|
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: popular parish missions | Statement: [Redemptorists, notableApostolate, popular parish missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableApostolate Context triple: [Redemptorists, notableApostolate, popular parish missions]
-
A.
notableAbbot
Indicates that a person is recognized as a distinguished or historically significant abbot.
-
B.
notableMonk
Indicates that a person is recognized as a monk of particular significance, prominence, or historical importance.
-
C.
notableOrdinary
Indicates that an entity is notable or significant despite being otherwise ordinary or typical in its category.
-
D.
notableBishop
Indicates that a person holds or held the position of bishop and is recognized as particularly significant or distinguished in that role.
-
E.
notableTheologianTradition
Indicates that a theologian is notably associated with, or recognized as a significant figure within, a particular religious or theological tradition.
- F. None of above. chosen
Provenance (4 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708d1fb88190bb33b72d4330ce11 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:22 p.m.