Triple
T34292003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurdwara Mal Ji Sahib |
E879915
|
entity |
| Predicate | primaryScriptureRecited |
P70785
|
FINISHED |
| Object | Guru Granth Sahib |
E56040
|
NE 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: Guru Granth Sahib | Statement: [Gurdwara Mal Ji Sahib, primaryScriptureRecited, Guru Granth Sahib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScriptureRecited Context triple: [Gurdwara Mal Ji Sahib, primaryScriptureRecited, Guru Granth Sahib]
-
A.
primaryScriptureOfReligion
Indicates that a given text serves as the main or authoritative scripture for a particular religion.
-
B.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
-
C.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
D.
scriptureRead
chosen
Indicates that an entity reads, studies, or engages with a religious or sacred text.
-
E.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
- F. None of above.
Provenance (4 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfcb3d5881909eb8f93e23d4323a |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.