Triple
T352040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Downfall |
E7463
|
entity |
| Predicate | plannedStartTime |
P288
|
FINISHED |
| Object | late 1945 |
—
|
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: late 1945 | Statement: [Operation Downfall, plannedStartTime, late 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedStartTime Context triple: [Operation Downfall, plannedStartTime, late 1945]
-
A.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
E.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7f1be88190964ddcbb6a05f021 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.