Triple
T17990181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G5 howitzer |
E430345
|
entity |
| Predicate | maximumRangeWithRocketAssistedAmmunition |
P128887
|
FINISHED |
| Object | over 40 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: over 40 km | Statement: [G5 howitzer, maximumRangeWithRocketAssistedAmmunition, over 40 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeWithRocketAssistedAmmunition Context triple: [G5 howitzer, maximumRangeWithRocketAssistedAmmunition, over 40 km]
-
A.
artilleryRange
chosen
Indicates that one entity is within the effective firing distance of another entity’s artillery.
-
B.
missileRange
Indicates the maximum distance over which a missile can effectively travel to reach and engage a target.
-
C.
suborbitalRange
Indicates the maximum distance or extent that something can travel or operate along a suborbital trajectory.
-
D.
missileLength
Indicates the physical longitudinal measurement of a missile from one end to the other.
-
E.
rocketCaliber
Indicates the diameter or size classification of a rocket, typically specifying the width of its body or projectile.
- 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.