Triple
T38048148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakk Nanaki |
E949676
|
entity |
| Predicate | foundingReligionContext |
P4028
|
FINISHED |
| Object | Sikh community |
—
|
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: Sikh community | Statement: [Chakk Nanaki, foundingReligionContext, Sikh community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingReligionContext Context triple: [Chakk Nanaki, foundingReligionContext, Sikh community]
-
A.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
B.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
-
C.
religionFoundedOn
Indicates that a particular religion is based on, derived from, or established according to a specific doctrine, text, tradition, or foundational principle.
-
D.
religiousAffiliationAtFoundation
chosen
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
-
E.
containsMajorReligionOrigin
Indicates that a location is the place where a major religion first originated or was founded.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:20 p.m.