Triple
T12749575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waheguru |
E304693
|
entity |
| Predicate | relationshipToCreation |
P16617
|
FINISHED |
| Object | both within creation and beyond creation |
—
|
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: both within creation and beyond creation | Statement: [Waheguru, relationshipToCreation, both within creation and beyond creation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCreation Context triple: [Waheguru, relationshipToCreation, both within creation and beyond creation]
-
A.
relationToCreation
chosen
Indicates the nature of a connection or involvement an entity has with the origin, production, or bringing-into-existence of something.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipToChildren
Indicates the type of familial or social connection an entity has to one or more children.
-
D.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
- 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.