Triple
T24899589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantsir-S1 |
E623535
|
entity |
| Predicate | maximumEngagementRange_guns_km |
P152572
|
FINISHED |
| Object | approximately 4 |
—
|
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 4 | Statement: [Pantsir-S1, maximumEngagementRange_guns_km, approximately 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumEngagementRange_guns_km Context triple: [Pantsir-S1, maximumEngagementRange_guns_km, approximately 4]
-
A.
hasFiringRange
chosen
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
B.
artilleryRange
Indicates that one entity is within the effective firing distance of another entity’s artillery.
-
C.
typicalShootingDistances
Indicates the usual or standard distances at which shooting (e.g., with a weapon or camera) typically occurs in a given context.
-
D.
gunElevationRange
Indicates the range of vertical angles through which a gun can be elevated or depressed relative to a reference plane.
-
E.
radarDetectionRange_km
Indicates the maximum distance in kilometers at which a radar system can detect a target.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:26 a.m.