Triple
T20670874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British peerage system |
E508018
|
entity |
| Predicate | includesGenderedTitle |
P1805
|
FINISHED |
| Object | duchess |
—
|
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: duchess | Statement: [British peerage system, includesGenderedTitle, duchess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGenderedTitle Context triple: [British peerage system, includesGenderedTitle, duchess]
-
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.
usedBothMaleAndFemaleTitles
Indicates that an entity has been referred to or addressed using both male and female honorifics or titles.
-
C.
honorificGender
Indicates that a particular honorific or title is associated with a specific gender or gendered form.
-
D.
namedForGender
Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
-
E.
genderedFormOf
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c92aa8819096fbe0ca5101d01b |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.