Triple
T28690441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomasz Kulik |
E729264
|
entity |
| Predicate | isNotableNamesakeOf |
P106994
|
FINISHED |
| Object | Kulik (surname) |
—
|
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 (surname) | Statement: [Tomasz Kulik, isNotableNamesakeOf, Kulik (surname)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotableNamesakeOf Context triple: [Tomasz Kulik, isNotableNamesakeOf, Kulik (surname)]
-
A.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
B.
notableAsNamesakeOf
chosen
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
C.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
-
D.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65684223c8190867c123acf504527 |
completed | May 2, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:35 a.m.