Triple
T4520171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamsa |
E103245
|
entity |
| Predicate | linkedDeityAspect |
P32453
|
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: [Hamsa, linkedDeityAspect, Brahma as creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDeityAspect Context triple: [Hamsa, linkedDeityAspect, Brahma as creator]
-
A.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
B.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
C.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
D.
integratesDeity
chosen
Indicates that one entity incorporates, assimilates, or unifies a deity or divine aspect into itself or into a larger system.
-
E.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5747e90c81908fa112ecace699a9 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.