Triple
T17980632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padmavati |
E449591
|
entity |
| Predicate | maritalStatusInMythology |
P47938
|
FINISHED |
| Object | wife of Venkateswara |
—
|
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: wife of Venkateswara | Statement: [Padmavati, maritalStatusInMythology, wife of Venkateswara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusInMythology Context triple: [Padmavati, maritalStatusInMythology, wife of Venkateswara]
-
A.
maritalStatusInMyth
chosen
Indicates the marital status or relationship state of an entity as portrayed within a specific myth or mythological tradition.
-
B.
marriageCharacterization
Indicates how a marriage is described, evaluated, or characterized in terms of its qualities, dynamics, or nature.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.