Triple
T33712036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Żółkiewski family |
E863766
|
entity |
| Predicate | genderedSurnameForm |
P17779
|
FINISHED |
| Object | Żółkiewska |
—
|
NE NERFINISHED |
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: Żółkiewska | Statement: [Żółkiewski family, genderedSurnameForm, Żółkiewska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderedSurnameForm Context triple: [Żółkiewski family, genderedSurnameForm, Żółkiewska]
-
A.
genderedFamilyName
Indicates that a family name is specifically associated with, or varies according to, a particular gender.
-
B.
genderedFormOf
chosen
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
-
C.
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.
-
D.
genderNeutralForm
Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
-
E.
genderedPluralForm
Indicates that the plural form of a term is specifically marked or inflected to reflect a particular gender.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.