Triple
T31883420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagyová |
E813941
|
entity |
| Predicate | followsSlavicSurnamePattern |
P195358
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nagyová, followsSlavicSurnamePattern, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSlavicSurnamePattern Context triple: [Nagyová, followsSlavicSurnamePattern, yes]
-
A.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
B.
isPatronymicOrToponymic
Indicates that a name or term is derived either from a person's name (patronymic) or from a place name (toponymic).
-
C.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
D.
isEquivalentSurnameInPolish
Indicates that two surnames are equivalent to each other when translated, adapted, or used in the Polish language.
-
E.
isPatronymicIn
Indicates that a name or term is used as a patronymic within a specified language, culture, or naming system.
- F. None of above. chosen
Provenance (4 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 30, 2026, 11:56 p.m.