Triple
T18232209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karol Lipiński |
E436569
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Karol Lipiński |
—
|
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: Karol Lipiński | Statement: [Karol Lipiński, name, Karol Lipiński]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karol Lipiński Context triple: [Karol Lipiński, name, Karol Lipiński]
-
A.
Karol Lipiński
chosen
Karol Lipiński was a prominent 19th-century Polish violinist and composer renowned as one of the leading virtuosos of his time.
-
B.
Piotr Lipiński
Piotr Lipiński is a Polish writer and journalist known for his historical reportage and works on 20th-century Polish history.
-
C.
Tomasz Kulik
Tomasz Kulik is a person notable enough to be recognized as a distinct namesake of the surname Kulik.
-
D.
Marek Lipski
Marek Lipski is an individual notable enough to be recognized as a bearer of the surname Lipski, though specific widely known public details about him are not readily available.
-
E.
Karol Klimczak
Karol Klimczak is a Polish football executive best known for leading top-flight club Lech Poznań.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b414308190bc7dd8e73c0a362c |
completed | April 19, 2026, 3:28 p.m. |
Created at: April 10, 2026, 10:33 a.m.