Triple
T2911664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peenemünde Army Research Center |
E63694
|
entity |
| Predicate | resultOfBombing |
P42871
|
FINISHED |
| Object | disruption of V-2 development |
—
|
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 V-2 development | Statement: [Peenemünde Army Research Center, resultOfBombing, disruption of V-2 development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBombing Context triple: [Peenemünde Army Research Center, resultOfBombing, disruption of V-2 development]
-
A.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
B.
cityBombed
Indicates that a particular city was subjected to a bombing attack.
-
C.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
D.
numberOfPeopleKilledInBombing
Indicates the total count of people who were killed as a direct result of a specific bombing event.
-
E.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.