Triple
T4738823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trimurti |
E105188
|
entity |
| Predicate | associatedWithDeityRole |
P51786
|
FINISHED |
| Object | Brahma as creator |
—
|
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: Brahma as creator | Statement: [Trimurti, associatedWithDeityRole, Brahma as creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDeityRole Context triple: [Trimurti, associatedWithDeityRole, Brahma as creator]
-
A.
associatedReligionRole
chosen
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
B.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
-
C.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
involvesDeity
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6485d690819098dc4a974516da6b |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.