Triple
T28917231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Heaven Church |
E733402
|
entity |
| Predicate | worshipCommunityType |
P89734
|
FINISHED |
| Object | parish community |
—
|
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: parish community | Statement: [Queen of Heaven Church, worshipCommunityType, parish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipCommunityType Context triple: [Queen of Heaven Church, worshipCommunityType, parish community]
-
A.
worshipperCommunity
chosen
Indicates that one entity is a community or group of people who collectively worship or devote religious reverence to another entity.
-
B.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
D.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
E.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 8:16 a.m.