Triple
T23059038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Kozłowiecki |
E574243
|
entity |
| Predicate | isHolocaustSurvivor |
P96743
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Adam Kozłowiecki, isHolocaustSurvivor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHolocaustSurvivor Context triple: [Adam Kozłowiecki, isHolocaustSurvivor, true]
-
A.
onlySurvivingImmediateMemberAfterHolocaust
Indicates that the subject is the sole remaining member of their immediate family who survived the Holocaust.
-
B.
survivedHolocaustAsChild
Indicates that the person lived through the Holocaust during their childhood.
-
C.
roleInHolocaust
Indicates that an entity had a specific involvement, function, or participation in events or activities related to the Holocaust.
-
D.
isSurvivorOf
chosen
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
E.
numberOfJewsSaved
Indicates the quantity of Jewish individuals who were rescued or preserved from harm, danger, or persecution in a given context.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1899e6c788190a2a862122cae8dc3 |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.