Triple
T7492642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucien Memorial United Methodist Church |
E177041
|
entity |
| Predicate | hasWorshipServices |
P77850
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lucien Memorial United Methodist Church, hasWorshipServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorshipServices Context triple: [Lucien Memorial United Methodist Church, hasWorshipServices, yes]
-
A.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
B.
hasLiturgicalCelebration
Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
-
C.
hasWorshipSpaceFeature
Indicates that a worship space possesses or includes a particular feature, characteristic, or facility.
-
D.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
E.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:43 p.m.