Triple
T1638150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müller |
E35404
|
entity |
| Predicate | isEquivalentSurnameInPolish |
P30820
|
FINISHED |
| Object | Młynarz |
—
|
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: Młynarz | Statement: [Müller, isEquivalentSurnameInPolish, Młynarz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEquivalentSurnameInPolish Context triple: [Müller, isEquivalentSurnameInPolish, Młynarz]
-
A.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
B.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
C.
isOccupationalSurname
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
D.
isAmongMostCommonSurnamesIn
Indicates that a surname ranks within the group of most frequently occurring surnames in a specified region or population.
-
E.
officialNamePolish
Indicates the official or legally recognized name of an entity as expressed in the Polish language.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:28 p.m.