Triple
T352066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Downfall |
E7463
|
entity |
| Predicate | plannedAirSupport |
P6269
|
FINISHED |
| Object | strategic bombing of Japan |
—
|
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: strategic bombing of Japan | Statement: [Operation Downfall, plannedAirSupport, strategic bombing of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedAirSupport Context triple: [Operation Downfall, plannedAirSupport, strategic bombing of Japan]
-
A.
notableAirOperation
Indicates that there is a significant or historically important air operation associated with the subject.
-
B.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
C.
airSupport
chosen
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
D.
airliftOrganizedBy
Indicates that an airlift operation is planned, coordinated, or managed by a specified organizing entity.
-
E.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
- 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.