Triple
T21396196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Anne’s Episcopal School |
E527788
|
entity |
| Predicate | hasChapelOrWorship |
P1191
|
FINISHED |
| Object | regular Episcopal chapel services |
—
|
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: regular Episcopal chapel services | Statement: [St. Anne’s Episcopal School, hasChapelOrWorship, regular Episcopal chapel services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapelOrWorship Context triple: [St. Anne’s Episcopal School, hasChapelOrWorship, regular Episcopal chapel services]
-
A.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
B.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
C.
hasChapelNearby
Indicates that one entity is located close to or in the vicinity of a chapel.
-
D.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
-
E.
hasChapels
Indicates that one entity contains, includes, or is associated with one or more chapels.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b11981388190874b8466400b39fe |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:13 p.m.