Triple
T23382187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple du Change |
E593776
|
entity |
| Predicate | openForReligiousServices |
P100760
|
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: [Temple du Change, openForReligiousServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openForReligiousServices Context triple: [Temple du Change, openForReligiousServices, yes]
-
A.
openForWorship
chosen
Indicates that a place of worship is currently available and accessible for religious services or devotional activities.
-
B.
allowsReligiousParticipation
Indicates that one entity grants another entity the permission or opportunity to take part in religious activities, practices, or institutions.
-
C.
hasWorshipServices
Indicates that an entity conducts or provides organized religious worship services.
-
D.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
E.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b9287481908fd86c41f6d9fc53 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:34 p.m.