Triple
T9165938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yefimovich |
E219955
|
entity |
| Predicate | nameGenderForm |
P17779
|
FINISHED |
| Object | masculine patronymic |
—
|
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: masculine patronymic | Statement: [Yefimovich, nameGenderForm, masculine patronymic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameGenderForm Context triple: [Yefimovich, nameGenderForm, masculine patronymic]
-
A.
genderNeutralForm
Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
-
B.
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.
-
C.
genderedFormOf
chosen
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
-
D.
hasFemaleFormOf
Indicates that one entity is the specifically female version or form of another, more general or differently gendered entity.
-
E.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa3055048190870211449c78fc4e |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.