Triple
T29928437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friends Academy |
E760147
|
entity |
| Predicate | meetingForWorship |
P3082
|
FINISHED |
| Object | practiced |
—
|
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: practiced | Statement: [Friends Academy, meetingForWorship, practiced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingForWorship Context triple: [Friends Academy, meetingForWorship, practiced]
-
A.
openForWorship
Indicates that a place of worship is currently available and accessible for religious services or devotional activities.
-
B.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
C.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
D.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
E.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677cdf7c081908af7be4259c7c615 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:17 p.m.