Triple
T7255814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwerer Gustav |
E157718
|
entity |
| Predicate | reasonForDestruction |
P13074
|
FINISHED |
| Object | to prevent capture by advancing Allied forces |
—
|
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: to prevent capture by advancing Allied forces | Statement: [Schwerer Gustav, reasonForDestruction, to prevent capture by advancing Allied forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDestruction Context triple: [Schwerer Gustav, reasonForDestruction, to prevent capture by advancing Allied forces]
-
A.
reasonForDemolition
chosen
Indicates the cause, justification, or circumstance that led to a structure or object being demolished.
-
B.
purposeOfDestruction
Indicates that something is destroyed with the specific aim or intention of achieving a particular goal or outcome.
-
C.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
D.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
E.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa0c76c81909fe43ed6938a13ea |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.