Triple
T37737189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagavat |
E940306
|
entity |
| Predicate | denotesBeingWith |
P2830
|
FINISHED |
| Object | six divine opulences |
—
|
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: six divine opulences | Statement: [Bhagavat, denotesBeingWith, six divine opulences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesBeingWith Context triple: [Bhagavat, denotesBeingWith, six divine opulences]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
C.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
D.
staysWith
Indicates that one entity remains in the company or presence of another entity for a period of time.
-
E.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.