Triple
T32993856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharawal |
E844166
|
entity |
| Predicate | hasTitleGender |
P1805
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Maharawal, hasTitleGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleGender Context triple: [Maharawal, hasTitleGender, male]
-
A.
hasGenderedTitle
chosen
Indicates that an entity is associated with a title or form of address that is explicitly marked for a particular gender.
-
B.
oppositeTitleByGender
Indicates that one title is the gender-based counterpart of another title (e.g., king/queen, actor/actress).
-
C.
usedBothMaleAndFemaleTitles
Indicates that an entity has been referred to or addressed using both male and female honorifics or titles.
-
D.
titleHolderSex
Indicates the biological or identified sex of the person who holds a particular title.
-
E.
hasMaleLineTitle
Indicates that a title is inherited or held exclusively through an unbroken male lineage from one male ancestor to his male descendants.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:22 a.m.