Triple
T10684123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invasion of the Kanto Plain (planned) |
E251830
|
entity |
| Predicate | plannedTimeframe |
P9416
|
FINISHED |
| Object | post-Operation Olympic period |
—
|
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: post-Operation Olympic period | Statement: [Invasion of the Kanto Plain (planned), plannedTimeframe, post-Operation Olympic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedTimeframe Context triple: [Invasion of the Kanto Plain (planned), plannedTimeframe, post-Operation Olympic period]
-
A.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
plannedFrom
Indicates that something is scheduled or arranged to originate, start, or be derived from a specified source, time, or condition.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
E.
timePeriodProposed
chosen
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc5134c8190bcb1d96a32634c17 |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.