Triple
T3376851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Mobility Artillery Rocket System |
E71084
|
entity |
| Predicate | maximumRangeWithATACMS |
P14301
|
FINISHED |
| Object | about 300 kilometers |
—
|
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: about 300 kilometers | Statement: [High Mobility Artillery Rocket System, maximumRangeWithATACMS, about 300 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeWithATACMS Context triple: [High Mobility Artillery Rocket System, maximumRangeWithATACMS, about 300 kilometers]
-
A.
maximumExtent
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
B.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
C.
maximumPanelSize
Indicates the largest allowable or supported size for a given panel in the specified context.
-
D.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
-
E.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e776508190bc123fb17b36f062 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.