Triple
T6718422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maghrib |
E153331
|
entity |
| Predicate | performedInCongregation |
P28132
|
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: [Maghrib, performedInCongregation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInCongregation Context triple: [Maghrib, performedInCongregation, 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.
canBePrayedInCongregation
chosen
Indicates that the action or ritual can be performed collectively as a group worship or prayer, rather than only individually.
-
C.
hasLiturgicalCelebration
Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
-
D.
establishedAsCongregationBy
Indicates that an entity was formally created or organized as a congregation by another specified agent or authority.
-
E.
consecratedInPresenceOf
Indicates that the act of consecration was performed while a specified person, group, or entity was present as a witness or participant.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d135d27c819088c45839ad0e7bab |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.