Triple
T21938832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramgarhia Sabha |
E541761
|
entity |
| Predicate | religiousServicesType |
P47539
|
FINISHED |
| Object | Sikh prayers |
—
|
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: Sikh prayers | Statement: [Ramgarhia Sabha, religiousServicesType, Sikh prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousServicesType Context triple: [Ramgarhia Sabha, religiousServicesType, Sikh prayers]
-
A.
religiousServiceType
chosen
Indicates the specific kind or category of religious service associated with an event or context.
-
B.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
C.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
liturgicalServices
Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity or context.
-
E.
religiousSupportType
Indicates the type or form of support provided or received in a religious or faith-based 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241f582c81909a244419cec38b19 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.