Triple
T34884608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сёмин |
E1006108
|
entity |
| Predicate | гендерная форма |
P17779
|
FINISHED |
| Object | мужская форма фамилии |
—
|
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: мужская форма фамилии | Statement: [Сёмин, гендерная форма, мужская форма фамилии]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: гендерная форма Context triple: [Сёмин, гендерная форма, мужская форма фамилии]
-
A.
genderedFormOf
chosen
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
-
B.
genderNeutralForm
Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
-
C.
genderedPluralForm
Indicates that the plural form of a term is specifically marked or inflected to reflect a particular gender.
-
D.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
E.
hasGenderInRussian
Indicates that an entity is associated with a specific grammatical gender in the Russian language.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.