Triple
T28051407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rozhdestvensky |
E708829
|
entity |
| Predicate | hasFeminineVariant |
P78555
|
FINISHED |
| Object | Rozhdestvenskaya |
—
|
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: Rozhdestvenskaya | Statement: [Rozhdestvensky, hasFeminineVariant, Rozhdestvenskaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeminineVariant Context triple: [Rozhdestvensky, hasFeminineVariant, Rozhdestvenskaya]
-
A.
hasFeminineFormInSomeLanguages
Indicates that the referenced entity has a distinct feminine grammatical or lexical form in at least one language.
-
B.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
-
C.
hasFemaleFormOf
chosen
Indicates that one entity is the specifically female version or form of another, more general or differently gendered entity.
-
D.
hasMasculineForm
Indicates that an entity has a corresponding masculine grammatical or lexical form.
-
E.
hasAlternativeGenderUsage
Indicates that an entity is used with a different or non-standard gender form in certain contexts or usages.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 8:33 p.m.