Triple
T12749574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waheguru |
E304693
|
entity |
| Predicate | centralToDoctrine |
P5485
|
FINISHED |
| Object | Sikh monotheism |
—
|
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 monotheism | Statement: [Waheguru, centralToDoctrine, Sikh monotheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToDoctrine Context triple: [Waheguru, centralToDoctrine, Sikh monotheism]
-
A.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
B.
createdDoctrine
Indicates that an entity originated, formulated, or established a particular doctrine, theory, or set of principles.
-
C.
proposesDoctrine
Indicates that one entity formally puts forward or advocates a particular doctrine, theory, or set of principles for consideration or adoption by others.
-
D.
concernsDoctrine
chosen
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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.