Triple
T11020817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirpal |
E260481
|
entity |
| Predicate | religiousUsage |
P56479
|
FINISHED |
| Object | often used by Sikhs |
—
|
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: often used by Sikhs | Statement: [Kirpal, religiousUsage, often used by Sikhs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousUsage Context triple: [Kirpal, religiousUsage, often used by Sikhs]
-
A.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
B.
isUsedByReligion
chosen
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
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.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bb6eec81909d8004af31f307f7 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.