Triple
T224628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treblinka |
E4287
|
entity |
| Predicate | uprisingDescription |
P4698
|
FINISHED |
| Object | armed revolt by prisoners |
—
|
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: armed revolt by prisoners | Statement: [Treblinka, uprisingDescription, armed revolt by prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uprisingDescription Context triple: [Treblinka, uprisingDescription, armed revolt by prisoners]
-
A.
uprising
chosen
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
B.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
-
C.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
D.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
E.
involvedIndependenceMovement
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.