Triple
T8271263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulik |
E193432
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object | Marek Kulik |
E731123
|
NE 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: Marek Kulik | Statement: [Kulik, hasNotableBearer, Marek Kulik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marek Kulik Context triple: [Kulik, hasNotableBearer, Marek Kulik]
-
A.
Marek Chodor
Marek Chodor is an architect known for designing the Bełżec memorial and museum commemorating victims of the Holocaust in Poland.
-
B.
Tomasz Kulik
Tomasz Kulik is a person notable enough to be recognized as a distinct namesake of the surname Kulik.
-
C.
Marek Janowski
Marek Janowski is a renowned Polish-born German conductor particularly celebrated for his interpretations of the German Romantic and Wagnerian operatic repertoire.
-
D.
Andrzej Kulik
chosen
Andrzej Kulik is a person notable enough to be specifically referenced as a bearer of the surname Kulik, though detailed public information about his life or achievements is limited.
-
E.
Marek Belka
Marek Belka is a Polish economist and politician who served as Prime Minister of Poland and later as president of the National Bank of Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7986f8cc8190a529dda980dd6e98 |
completed | March 31, 2026, 7:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1cd748708190a353469043f3046a |
completed | April 2, 2026, 7:37 a.m. |
Created at: March 30, 2026, 5:50 p.m.