Triple
T348259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampfgeschwader 53 |
E6986
|
entity |
| Predicate | usedTactics |
P3047
|
FINISHED |
| Object | area bombing |
—
|
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: area bombing | Statement: [Kampfgeschwader 53, usedTactics, area bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTactics Context triple: [Kampfgeschwader 53, usedTactics, area bombing]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.