Triple
T3054222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łódź Ghetto |
E60440
|
entity |
| Predicate | containsPopulation |
P2750
|
FINISHED |
| Object | Polish Jews |
—
|
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: Polish Jews | Statement: [Łódź Ghetto, containsPopulation, Polish Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPopulation Context triple: [Łódź Ghetto, containsPopulation, Polish Jews]
-
A.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
-
B.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
C.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
D.
populationIncludes
chosen
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
E.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf51b5081908ce355a76cfa9e3c |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.