Triple

T28355539
Position Surface form Disambiguated ID Type / Status
Subject Kamiński E718215 entity
Predicate hasNotableBearer P458 FINISHED
Object Kazimierz Kamiński
Kazimierz Kamiński is a personal name associated with multiple Polish individuals, likely of some local or historical significance.
E2065915 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: Kazimierz Kamiński | Statement: [Kamiński, hasNotableBearer, Kazimierz Kamiński]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kazimierz Kamiński
Triple: [Kamiński, hasNotableBearer, Kazimierz Kamiński]
Generated description
Kazimierz Kamiński is a personal name associated with multiple Polish individuals, likely of some local or historical significance.

Provenance (5 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_69eff6ec27b481908c8d7b86c47893d9 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64c2ccd8c819099051395954582ca completed May 2, 2026, 7:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a365c4e48c081909c89d9fc7a13b789 completed June 20, 2026, 9:24 a.m.
NEDg Description generation batch_6a365dcf9e188190984b5728842ec459 completed June 20, 2026, 9:30 a.m.
NED2 Entity disambiguation (via description) batch_6a365f8e761c819088a969d0180fb5e7 completed June 20, 2026, 9:38 a.m.
Created at: April 28, 2026, 12:49 a.m.