Triple
T12749571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waheguru |
E304693
|
entity |
| Predicate | meaningAsUnderstoodBySikhs |
P94973
|
FINISHED |
| Object | Wonderful Lord |
—
|
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: Wonderful Lord | Statement: [Waheguru, meaningAsUnderstoodBySikhs, Wonderful Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningAsUnderstoodBySikhs Context triple: [Waheguru, meaningAsUnderstoodBySikhs, Wonderful Lord]
-
A.
roleInSikhTradition
Indicates the specific function, status, or position an entity holds within Sikh religious, cultural, or historical practices and institutions.
-
B.
hasMeaningInSanskrit
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Sanskrit language.
-
C.
scriptForSikhReligiousTexts
Indicates the script or writing system used to write Sikh religious texts.
-
D.
fifthGuruOfSikhs
Indicates that one entity is the fifth spiritual leader (Guru) in the historical succession of Sikh Gurus in relation to the Sikh community.
-
E.
fatehMeaning
chosen
Indicates that one entity conveys or expresses the meaning, interpretation, or semantic content of another.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.