Triple
T455940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulag system |
E7231
|
entity |
| Predicate | estimatedPrisonerCount |
P14018
|
FINISHED |
| Object | millions |
—
|
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: millions | Statement: [Gulag system, estimatedPrisonerCount, millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedPrisonerCount Context triple: [Gulag system, estimatedPrisonerCount, millions]
-
A.
placeOfDetention
Indicates the location or facility where an entity is or was held in detention.
-
B.
estimatedNumberOfSurvivorsAtLiberation
Indicates the approximate count of individuals who were still alive at the time a camp or similar site was liberated.
-
C.
wasImprisonedIn
Indicates that an entity was held in confinement or incarcerated at a particular place or facility.
-
D.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
E.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
- F. None of above. chosen
Provenance (4 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef9f772c8190863399c5ee1378fe |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeeb85f881909580a6a86332b4a5 |
completed | Feb. 28, 2026, 1:34 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.