Triple
T34805657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talavan |
E1003346
|
entity |
| Predicate | associatedWithFormOfGod |
P102272
|
FINISHED |
| Object | Krishna |
E18565
|
NE 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: Krishna | Statement: [Talavan, associatedWithFormOfGod, Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFormOfGod Context triple: [Talavan, associatedWithFormOfGod, Krishna]
-
A.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
B.
associatedDeityOrForce
chosen
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
C.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
D.
associatedFormOfShiva
Indicates a relationship where one entity is a particular form, aspect, or manifestation that is traditionally associated with the deity Shiva.
-
E.
associatedFormOfDevi
Indicates a relationship where one form or variant of a deity is linked or connected to another, typically as an alternate or associated manifestation.
- F. None of above.
Provenance (4 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fadb1b081909b7d30bfd3b7ca43 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.