Triple
T10569933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity Episcopal Church, Swarthmore |
E249451
|
entity |
| Predicate | offersMinistry |
P94699
|
FINISHED |
| Object | worship |
—
|
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: worship | Statement: [Trinity Episcopal Church, Swarthmore, offersMinistry, worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersMinistry Context triple: [Trinity Episcopal Church, Swarthmore, offersMinistry, worship]
-
A.
worshipersOffer
Indicates that worshipers present or dedicate offerings to a deity, sacred figure, or religious object.
-
B.
supportedMinistryOf
Indicates that one entity provided assistance, endorsement, or resources to help carry out the ministry or religious service activities of another entity.
-
C.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
D.
supportedMinistryIn
Indicates that an entity provided support to a ministry operating within a specified location or jurisdiction.
-
E.
sharesMinistryAmong
Indicates that a ministry or ministerial responsibility is jointly held, distributed, or exercised among multiple entities.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52730fd4481908b3f4eb80ca209f2 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.