Triple
T21211828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadtal Gadi |
E522738
|
entity |
| Predicate | hasLanguageOfReligiousActivity |
P3115
|
FINISHED |
| Object | Gujarati |
—
|
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: Gujarati | Statement: [Vadtal Gadi, hasLanguageOfReligiousActivity, Gujarati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfReligiousActivity Context triple: [Vadtal Gadi, hasLanguageOfReligiousActivity, Gujarati]
-
A.
hasReligiousObservance
Indicates that an entity practices, observes, or participates in a particular religious rite, ceremony, or tradition.
-
B.
languageOfWorship
chosen
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
usedForReligiousLanguage
Indicates that something is employed specifically in the context of religious language, such as for expressing, communicating, or performing religious beliefs, practices, or rituals.
-
E.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7346eb20c8190aeb3c0cc0a24aaf9 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:37 p.m.