Triple
T11274838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7.5 cm StuK 37 L/24 |
E266907
|
entity |
| Predicate | primaryAmmunitionType |
P6074
|
FINISHED |
| Object | high-explosive shell |
—
|
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: high-explosive shell | Statement: [7.5 cm StuK 37 L/24, primaryAmmunitionType, high-explosive shell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAmmunitionType Context triple: [7.5 cm StuK 37 L/24, primaryAmmunitionType, high-explosive shell]
-
A.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
B.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
D.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
E.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e966cb4c8190bc410d7e623e54db |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.