Triple
T33123261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominican Province of the Holy Rosary |
E847656
|
entity |
| Predicate | hasApostolateType |
P192857
|
FINISHED |
| Object | evangelization |
—
|
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: evangelization | Statement: [Dominican Province of the Holy Rosary, hasApostolateType, evangelization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApostolateType Context triple: [Dominican Province of the Holy Rosary, hasApostolateType, evangelization]
-
A.
isApostolicCongregation
Indicates that a religious community or congregation follows apostolic traditions, authority, or succession in its beliefs, practices, or governance.
-
B.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
C.
isApostolicWorkerIn
Indicates that a person serves or functions as an apostolic worker within a specified organization, community, or geographic area.
-
D.
hasApostle
Indicates that a person or deity is associated with, or has, one or more apostles devoted to following or spreading their teachings.
-
E.
hasParishType
Indicates that an entity is associated with or classified by a specific type or category of parish.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 1, 2026, 1:27 a.m.