Triple
T5242179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subhadra |
E118368
|
entity |
| Predicate | marriageForm |
P11275
|
FINISHED |
| Object | svayamvara-abduction narrative |
—
|
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: svayamvara-abduction narrative | Statement: [Subhadra, marriageForm, svayamvara-abduction narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageForm Context triple: [Subhadra, marriageForm, svayamvara-abduction narrative]
-
A.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
-
C.
marriageContext
Indicates the situational or cultural circumstances under which a marriage occurs or exists, such as legal, social, or religious conditions surrounding the marital relationship.
-
D.
marriagePattern
chosen
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
-
E.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.