Triple
T36835950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr family of rifles |
E910271
|
entity |
| Predicate | developedInConflict |
P155098
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Sturmgewehr family of rifles, developedInConflict, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInConflict Context triple: [Sturmgewehr family of rifles, developedInConflict, World War II]
-
A.
developedDuringConflict
chosen
Indicates that something was created, advanced, or significantly progressed while an identified conflict (such as a war, dispute, or crisis) was ongoing.
-
B.
builtDuringConflict
Indicates that the construction of one entity occurred while a specified conflict or war was taking place.
-
C.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
D.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
E.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:13 p.m.