Triple
T25328571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Cologne |
E635085
|
entity |
| Predicate | codenameOfNotableRaid |
P124342
|
FINISHED |
| Object | Operation Millennium |
—
|
NE NERFINISHED |
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: Operation Millennium | Statement: [bombing of Cologne, codenameOfNotableRaid, Operation Millennium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codenameOfNotableRaid Context triple: [bombing of Cologne, codenameOfNotableRaid, Operation Millennium]
-
A.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
B.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
C.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
-
D.
finalRaidEncounter
Indicates that an encounter represents the ultimate or concluding boss fight or challenge within a raid.
-
E.
invasionCodename
chosen
Indicates the codename assigned to a specific military invasion 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c2c7b081909a09153061b01fa7 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.