Triple
T35310110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höfle Telegram |
E1019745
|
entity |
| Predicate | numberReportedForLublinMajdanek |
P5134
|
FINISHED |
| Object | 24733 |
—
|
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: 24733 | Statement: [Höfle Telegram, numberReportedForLublinMajdanek, 24733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberReportedForLublinMajdanek Context triple: [Höfle Telegram, numberReportedForLublinMajdanek, 24733]
-
A.
ghettoSynagogueComplex
Indicates a relationship where a synagogue is part of, or associated with, a larger complex located within a Jewish ghetto.
-
B.
numberOfJewsKilled
chosen
Indicates the quantity of Jewish people who were killed in a given event, context, or time period.
-
C.
currentStatusAtAuschwitz
Indicates the person’s present condition, role, or situation specifically while at Auschwitz.
-
D.
concentrationCampDestination
Indicates that an entity is sent or transported to a concentration camp as its destination.
-
E.
associatedConcentrationCamp
Indicates a relationship where an entity is linked or connected to a specific concentration camp, typically by location, administration, or operational association.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.