Triple
T34111855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ik Oankar |
E874857
|
entity |
| Predicate | attributeOfGod |
P57193
|
FINISHED |
| Object | formless |
—
|
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: formless | Statement: [Ik Oankar, attributeOfGod, formless]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributeOfGod Context triple: [Ik Oankar, attributeOfGod, formless]
-
A.
attributeOfDeity
chosen
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
B.
theologicalAttribute
Indicates that one entity possesses or is characterized by a particular theological property, quality, or doctrinal attribute in relation to another.
-
C.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
D.
emphasizesAttributeOfAllah
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Allah.
-
E.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb544848190aaeb8f766a95aaff |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.