Triple
T27724798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revati |
E699063
|
entity |
| Predicate | husbandAspect |
P91240
|
FINISHED |
| Object | Balarama as Shesha incarnation |
—
|
NE NERFINISHED |
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: Balarama as Shesha incarnation | Statement: [Revati, husbandAspect, Balarama as Shesha incarnation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: husbandAspect Context triple: [Revati, husbandAspect, Balarama as Shesha incarnation]
-
A.
spouseCharacteristic
chosen
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
B.
attitudeTowardSpouse
Indicates a person's emotional or evaluative stance toward their spouse within the marital relationship.
-
C.
husbandStatus
Indicates that one person holds the social and/or legal role of husband in relation to another person.
-
D.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363f74248190966df10d3445b5ea |
completed | May 2, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:08 p.m.