Triple
T5336230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakti |
E123832
|
entity |
| Predicate | relationshipToShiva |
P60881
|
FINISHED |
| Object | consort of Shiva |
—
|
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: consort of Shiva | Statement: [Shakti, relationshipToShiva, consort of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToShiva Context triple: [Shakti, relationshipToShiva, consort of Shiva]
-
A.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
D.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.