Triple
T10555271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swarthmore Friends Meeting |
E249064
|
entity |
| Predicate | hasMeetingForWorship |
P77850
|
FINISHED |
| Object | First Day (Sunday) |
—
|
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: First Day (Sunday) | Statement: [Swarthmore Friends Meeting, hasMeetingForWorship, First Day (Sunday)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingForWorship Context triple: [Swarthmore Friends Meeting, hasMeetingForWorship, First Day (Sunday)]
-
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.
hasWorshipServices
chosen
Indicates that an entity conducts or provides organized religious worship services.
-
C.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
D.
hasMeetingSchedule
Indicates that an entity has an associated plan or timetable specifying when meetings are to occur.
-
E.
hasLiturgicalCelebration
Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52712a9988190bf63e7c47f6e6fc1 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.