Triple
T11691049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilian Kolbe |
E277867
|
entity |
| Predicate | AuschwitzPrisonerNumber |
P70633
|
FINISHED |
| Object | 16670 |
—
|
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: 16670 | Statement: [Maximilian Kolbe, AuschwitzPrisonerNumber, 16670]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AuschwitzPrisonerNumber Context triple: [Maximilian Kolbe, AuschwitzPrisonerNumber, 16670]
-
A.
prisonerNumber
chosen
Indicates that an entity is assigned a specific identification number used to uniquely identify them as a prisoner.
-
B.
laterPrisonerNumber
Indicates that one prisoner has a higher (and thus later-assigned) prisoner identification number than another prisoner.
-
C.
concentrationCampDestination
Indicates that an entity is sent or transported to a concentration camp as its destination.
-
D.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
E.
exterminationCamp
Indicates a facility specifically established and operated for the systematic mass murder and annihilation of targeted groups of people.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.