Triple
T28551437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krzysztof Kulik |
E722894
|
entity |
| Predicate | isBearerOfSurname |
P108409
|
FINISHED |
| Object | Kulik |
—
|
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: Kulik | Statement: [Krzysztof Kulik, isBearerOfSurname, Kulik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBearerOfSurname Context triple: [Krzysztof Kulik, isBearerOfSurname, Kulik]
-
A.
hasSurnameBearer
chosen
Indicates that a particular surname is borne or carried by a specific person or entity.
-
B.
isSurname
Indicates that one entity is the family name (last name) of another entity.
-
C.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
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.
-
E.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6504c5e1c8190903e5c4aeac37a30 |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:43 a.m.