Triple
T8090137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendicant orders |
E188835
|
entity |
| Predicate | typicalApostolate |
P12146
|
FINISHED |
| Object | preaching 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: preaching missions | Statement: [Mendicant orders, typicalApostolate, preaching missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApostolate Context triple: [Mendicant orders, typicalApostolate, preaching missions]
-
A.
apostolate
Indicates the relationship in which an individual or group carries out a mission of religious or spiritual outreach, service, or evangelization on behalf of a faith community.
-
B.
apostolicGroup
Indicates that an entity is a group characterized by an apostolic role, mission, or authority, typically linked to the work or tradition of apostles.
-
C.
leadApostle
Indicates that one entity serves as the primary or chief apostolic leader in relation to another entity.
-
D.
spiritualMinistry
Indicates that one entity provides religious or spiritual guidance, care, or services to another entity.
-
E.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421e30e88190b9699b338b69b81c |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.