Triple
T76094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmark Incident |
E1520
|
entity |
| Predicate | prisonersFreed |
P704
|
FINISHED |
| Object | 299 |
—
|
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: 299 | Statement: [Altmark Incident, prisonersFreed, 299]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prisonersFreed Context triple: [Altmark Incident, prisonersFreed, 299]
-
A.
estimatedNumberOfSurvivorsAtLiberation
Indicates the approximate count of individuals who were still alive at the time a camp or similar site was liberated.
-
B.
liberationEvent
chosen
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
C.
LiberationOfAuschwitz
Indicates the act or event of freeing prisoners and ending Nazi control at the Auschwitz concentration camp.
-
D.
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.
-
E.
slaveryAbolishedBy
Indicates that an instance of slavery was ended, prohibited, or legally abolished by a particular agent, authority, or entity.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2559892dc81909303f2eefdc0025f |
completed | Feb. 28, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69a24eaf99e481908e8d314577e22ecf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.