Triple
T34020440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taran Panth |
E872365
|
entity |
| Predicate | religiousMeetings |
P21643
|
FINISHED |
| Object | collective study of Taran Svami’s texts |
—
|
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: collective study of Taran Svami’s texts | Statement: [Taran Panth, religiousMeetings, collective study of Taran Svami’s texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousMeetings Context triple: [Taran Panth, religiousMeetings, collective study of Taran Svami’s texts]
-
A.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
B.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
C.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
E.
religiousEventRecognizedBy
Indicates that a religious event is formally acknowledged, validated, or accepted by a particular authority, group, or institution.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:51 a.m.