Triple
T17990179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G5 howitzer |
E430345
|
entity |
| Predicate | maximumRangeWithStandardAmmunition |
P83732
|
FINISHED |
| Object | approximately 30 km |
—
|
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: approximately 30 km | Statement: [G5 howitzer, maximumRangeWithStandardAmmunition, approximately 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeWithStandardAmmunition Context triple: [G5 howitzer, maximumRangeWithStandardAmmunition, approximately 30 km]
-
A.
rangeStandardAmmunition
chosen
Indicates that the relationship specifies the standard type of ammunition used for a given range or weapon system.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
gunElevationRange
Indicates the range of vertical angles through which a gun can be elevated or depressed relative to a reference plane.
-
D.
artilleryRange
Indicates that one entity is within the effective firing distance of another entity’s artillery.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29f127c81908b0c4cb3787e002c |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.