Triple
T6200892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dieppe Canadian War Cemetery |
E138625
|
entity |
| Predicate | primaryBurialDateRange |
P25906
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Dieppe Canadian War Cemetery, primaryBurialDateRange, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBurialDateRange Context triple: [Dieppe Canadian War Cemetery, primaryBurialDateRange, 1942]
-
A.
mainBurialsPeriodStart
chosen
Indicates the time period or date when the primary or main phase of burials at a site or within a context began.
-
B.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
C.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
D.
mainBurialsPeriodEnd
Indicates the time period or date when the primary phase of burials at a site or context came to an end.
-
E.
createdBetween
Indicates that something was created within a specified start and end time or date range.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062547cd48190a2715537b961262e |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.