Triple
T17374651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar B-24 crash of 4 July 1943 |
E422403
|
entity |
| Predicate | victimCategory |
P127243
|
FINISHED |
| Object | civilian and military passengers |
—
|
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: civilian and military passengers | Statement: [Gibraltar B-24 crash of 4 July 1943, victimCategory, civilian and military passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimCategory Context triple: [Gibraltar B-24 crash of 4 July 1943, victimCategory, civilian and military passengers]
-
A.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
B.
victimGroupContext
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
-
C.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
D.
victimGroupHelped
Indicates that assistance, support, or aid was provided to a group identified as victims.
-
E.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6b71148190bb10e1fac400d6c3 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.