Triple
T1075709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rana of Porbandar |
E23832
|
entity |
| Predicate | nobleTitleGender |
P13876
|
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: [Rana of Porbandar, nobleTitleGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleGender Context triple: [Rana of Porbandar, nobleTitleGender, male]
-
A.
hasGenderedTitle
Indicates that an entity is associated with a title or form of address that is explicitly marked for a particular gender.
-
B.
monarchTitleGenderedForm
chosen
Indicates the specific gendered version of a monarch’s title (e.g., king vs. queen) used to refer to that ruler.
-
C.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
nobleTitleNumber
Indicates the ordinal number or sequence position associated with a person's noble title (e.g., first duke, second baron).
-
E.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92e480c81909a848b48c196a293 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.