Triple
T12236928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 51st (Highland) Infantry Division |
E291618
|
entity |
| Predicate | fateIn1940 |
P23985
|
FINISHED |
| Object | surrendered at Saint-Valery-en-Caux |
—
|
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: surrendered at Saint-Valery-en-Caux | Statement: [51st (Highland) Infantry Division, fateIn1940, surrendered at Saint-Valery-en-Caux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateIn1940 Context triple: [51st (Highland) Infantry Division, fateIn1940, surrendered at Saint-Valery-en-Caux]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
-
C.
fateDuringFrenchRevolution
Indicates the outcome or destiny that befell an entity specifically during the period of the French Revolution.
-
D.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during World War II.
-
E.
WWIIEvent
chosen
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.