Triple
T26135568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Vaishnavite movement in Assam |
E659370
|
entity |
| Predicate | worshipSpaceType |
P71341
|
FINISHED |
| Object | community prayer hall |
—
|
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: community prayer hall | Statement: [Neo-Vaishnavite movement in Assam, worshipSpaceType, community prayer hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipSpaceType Context triple: [Neo-Vaishnavite movement in Assam, worshipSpaceType, community prayer hall]
-
A.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
B.
worshipArea
chosen
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
-
C.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
D.
worshipStyle
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
E.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 8:17 p.m.