Triple
T29211726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purattasi |
E740561
|
entity |
| Predicate | communityEvent |
P102091
|
FINISHED |
| Object | special satsangs and bhajan gatherings |
—
|
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: special satsangs and bhajan gatherings | Statement: [Purattasi, communityEvent, special satsangs and bhajan gatherings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityEvent Context triple: [Purattasi, communityEvent, special satsangs and bhajan gatherings]
-
A.
communityActivity
chosen
Indicates that an entity participates in, contributes to, or is involved with activities organized for or by a community.
-
B.
associatedCityEvent
Indicates a relationship where a city is linked to, involved in, or serves as the location for a particular event.
-
C.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
D.
communityOrganizations
Indicates that there is an association or involvement between entities and one or more community-based organizations or groups.
-
E.
weekendEvent
Indicates that an event occurs during the weekend period (typically Saturday and/or Sunday).
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:11 p.m.