Triple
T20810898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandodari |
E512296
|
entity |
| Predicate | husbandType |
P31663
|
FINISHED |
| Object | rakshasa king |
—
|
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: rakshasa king | Statement: [Mandodari, husbandType, rakshasa king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: husbandType Context triple: [Mandodari, husbandType, rakshasa king]
-
A.
spouseType
chosen
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
B.
spouseGender
Indicates the gender of a person’s spouse in a marital relationship.
-
C.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
D.
spouseCharacteristic
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d27a4881908b34679385d8b94b |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.