Triple
T19528013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bielefeld viaduct |
E488581
|
entity |
| Predicate | bombingObjective |
P136651
|
FINISHED |
| Object | disruption of German rail communications |
—
|
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: disruption of German rail communications | Statement: [Bielefeld viaduct, bombingObjective, disruption of German rail communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombingObjective Context triple: [Bielefeld viaduct, bombingObjective, disruption of German rail communications]
-
A.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
B.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
-
C.
bombardmentMilitaryTargets
Indicates the action of directing explosive or artillery attacks specifically against military objectives or installations.
-
D.
bombingPlatform
Indicates that one entity serves as the platform or means from which another entity conducts or carries out a bombing.
-
E.
bombBay
Indicates that an entity serves as or is located in the bomb bay compartment of an aircraft, where bombs are stored and released.
- F. None of above. chosen
Provenance (4 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363d43148190af25caaa57accf9b |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.