Triple
T28236499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Saskatchewan Regiment |
E711893
|
entity |
| Predicate | VictoriaCrossAction |
P136425
|
FINISHED |
| Object | Dieppe Raid |
—
|
NE NERFINISHED |
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: Dieppe Raid | Statement: [South Saskatchewan Regiment, VictoriaCrossAction, Dieppe Raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VictoriaCrossAction Context triple: [South Saskatchewan Regiment, VictoriaCrossAction, Dieppe Raid]
-
A.
victoriaCrossActionRole
Indicates the specific role or capacity in which an individual acted when performing the deed for which the Victoria Cross was awarded.
-
B.
numberOfVictoriaCrossesAwarded
Indicates the total count of Victoria Cross medals that have been awarded in the specified context.
-
C.
victoriaCrossActionLocation
chosen
Indicates the location where an action took place that led to the awarding of a Victoria Cross.
-
D.
victoriaCrossActionDate
Indicates the date on which the action or deed occurred that led to the awarding of the Victoria Cross.
-
E.
dateOfActionForVictoriaCross
Indicates the specific date on which the action occurred for which the Victoria Cross was awarded.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:55 p.m.