Triple
T38546206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joti Jot of Guru Gobind Singh |
E924968
|
entity |
| Predicate | hasReligiousCategory |
P104709
|
FINISHED |
| Object | Joti Jot of a Sikh Guru |
—
|
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: Joti Jot of a Sikh Guru | Statement: [Joti Jot of Guru Gobind Singh, hasReligiousCategory, Joti Jot of a Sikh Guru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousCategory Context triple: [Joti Jot of Guru Gobind Singh, hasReligiousCategory, Joti Jot of a Sikh Guru]
-
A.
hasReligiousType
chosen
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
B.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
C.
hasReligionDomain
Indicates that an entity is associated with, operates within, or pertains to a particular religious domain or sphere.
-
D.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
E.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.