Triple
T10799069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Villers-Bocage |
E254789
|
entity |
| Predicate | daysAfterEvent |
P89697
|
FINISHED |
| Object | 7 days after D-Day |
—
|
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: 7 days after D-Day | Statement: [Battle of Villers-Bocage, daysAfterEvent, 7 days after D-Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daysAfterEvent Context triple: [Battle of Villers-Bocage, daysAfterEvent, 7 days after D-Day]
-
A.
monthsBeforeEvent
Indicates that one temporal entity occurs a specified number of months before a referenced event.
-
B.
followsAfterNumberOfDays
chosen
Indicates that one event or state occurs after another by a specified number of days.
-
C.
occursNumberOfDaysBefore
Indicates that one event or time point happens a specified number of days earlier than another event or time point.
-
D.
timePeriodAfter
Indicates that one time period occurs entirely later than another time period in a temporal sequence.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73334feb08190aae967eaa37659f7 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.